Two ways to connect
Bitly now runs a hosted MCP server. Connect it and the agent can manage your links and pull analytics without needing a separate API setup.- Bitly MCP (recommended). Connect Bitly’s MCP server once and the agent can create short links and QR codes, pull click analytics, manage your link library. See Connect with MCP.
- Bitly OAuth. The original sign-in integration, scoped to what you grant. See Connect with OAuth.
What the agent can do
Create short links
Turn long URLs into short, shareable links.
Generate QR codes
Create QR codes tied to your short links.
Pull click analytics
See clicks by time, country, city, device, and referrer.
Manage links
Update destinations, titles, tags, and archive old links.
Example agent tasks
Connect with MCP
1
Add the Bitly connection
From the agent’s connections, choose Bitly. The platform connects you through Bitly’s MCP server.
2
Sign in to Bitly
A connect card appears. Sign in to your Bitly account and approve.
3
The agent gets to work
It can now create short links and QR codes, pull click analytics, manage your link library through the MCP server.
MCP is the first-class connection when both options are available. See Tools & MCP.
Connect with OAuth
What you share
During the connect flow you authorize what the agent can reach. It works only within what you grant. As with every connection, the underlying token is handled securely and never exposed to the model. See Permissioning.1
Authorize Bitly for the agent
From the agent’s connections, choose Bitly and sign in.
2
Approve the access
Confirm what the agent can reach. You can change this later.
3
The agent gets to work
It works through the secure proxy, within what you granted.
Learn more
Bitly developer docs
The full reference for what’s possible.
How credentials stay safe
The proxy model that keeps tokens out of the agent’s reach.