URLHopURLHop for AI assistants: ask, and your links get done
Tell Claude, ChatGPT, Cursor or any assistant that speaks MCP what you need: "make a QR code for the winter menu", "send iPhones to the App Store and Android to Google Play", "how many scans did the flyer get this week?". It does the work in your URLHop account, and you approve the connection once.
What you can ask an assistant to do
MCP (Model Context Protocol) is the open standard AI assistants use to work with other apps. Once URLHop is connected, the assistant can do in your workspace what you would do in the dashboard, only by conversation. The same validation, safety checks and plan limits apply as in the dashboard.
Examples of requests
- Create short links and dynamic QR codes, with a name you choose, and change the destination of a code that is already printed.
- Build and edit link-in-bio pages: title, buttons and order.
- Set rules by device, by country or A/B splits on a link, when your plan includes them.
- Read analytics: visits by day, country, device and referring site, and compare links.
- Check your plan and how much of it you have used.
- Open a support ticket or send feedback to the URLHop team, and read their answers, when you ask for it.
- See your Refer & earn link and how many days of Pro you have earned.
How to connect in about a minute
You do not need an API key or any code. In an assistant that supports custom connectors, you add URLHop as one.
Step by step
- In your assistant's settings, add a custom connector (or MCP server) with this address: https://app.urlhop.me/mcp
- Sign in to URLHop, or create a free account right there if you do not have one yet.
- Pick the workspace the assistant may use and approve on the consent screen. You can refuse, and nothing is connected.
- Ask for what you need. To disconnect, go to Settings → Connected apps in URLHop and revoke the app; access stops immediately.
Agents without a browser: a person always confirms
Some agents run without a browser, in a terminal or in the cloud. They can ask URLHop for an account on behalf of a person by giving that person's email address. URLHop emails the person, and nothing happens until they open the message, create the account or sign in, type the short confirmation code the agent shows them, and approve. If they do not, the request expires in 24 hours. Humans validate every account, so an agent never gets access to anyone's links by itself.
What an agent can and cannot do
An assistant acts only inside the workspace you chose and only up to what your plan allows: it cannot create more links than the plan includes or use a feature the plan does not have. Billing and plan changes, single sign-on, API keys, team roles and deleting the account stay with people, in the dashboard.
Security you can explain to your team
Connections use OAuth 2.1 with PKCE, the sign-in standard MCP clients follow. You approve each app separately on a consent screen. Access tokens are short-lived (one hour) and renewed automatically, and URLHop stores tokens only as hashes, so they cannot be read back. You can revoke any connected app at any time, and each connection is limited to one workspace.
Which plan includes it
Connecting an AI assistant works on every plan, including Free, which is free forever with no credit card. Plan limits still apply to what the assistant creates, and some features follow the plan: rules by device need Pro (and every new account has them during the 30-day free Pro trial), while rules by country and A/B tests need Business. The REST API with keys is separate and starts on Starter.