Bitly
by Bitly
Shorten links, build QR Codes and read click analytics from your AI assistant. An assistant with this connector can retarget an already-distributed short link to a new destination — Bitly documents that as a supported use.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Bitly via MCP
https://api-ssl.bitly.com/v4/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Use in Agentman
Connect Bitly once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioBitly Tools & Capabilities (27)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- A short link is public the moment it is created, and there is no undo for a distributed one. Deletion is restricted to unedited links, so the recovery path for a link that has been changed is archiving, not removal. Archiving does not retract a URL someone has already shared.
- Retargeting is silent by design. The short URL is unchanged when its destination changes, so no recipient can tell. Treat the link-update tool as the connector's highest-consequence call and keep a confirmation in front of it. No MCP annotation enforces that — the gate is your client's.
- Editing a link costs quota. Bitly's REST documentation states that updating a link always charges an encode limit, so an assistant looping over links consumes plan allowance on writes as well as creations.
- Two limit systems apply. Bitly documents platform limits — per-hour, per-minute and per-IP, with a maximum of five concurrent connections from one IP address — and separate monthly plan limits on API requests, links, custom back-halves and redirects. Breaching either returns a 429.
- Custom domains must already exist and be configured. The connector reads domains; it cannot create one. Bitly documents a DNS configuration step before a custom domain will shorten links, and an
INVALID_ARG_DOMAINerror when a group lacks access to the domain requested. - The token is tied to a person, not an organization. Bitly states that a token belongs to the user who created it, and that removing that user from the account breaks any integration using it.
- We could not read tool schemas or safety annotations. The endpoint returns 401 to an anonymous request, so parameter types and MCP safety hints are not published here.
- Bitly's own caching guidance is out of step with the connector. Its troubleshooting page tells API consumers that links never change or expire and to cache accordingly, while the link-update tool changes destinations. The tool reference is the accurate half; both were retrieved on the same date.
Frequently asked questions
Yes. Bitly's tool reference documents a link-update tool that accepts a destination URL, and gives changing a link's destination to a new page as one of its example prompts. The underlying REST operation states that to redirect a link, you use the long_url parameter. Anyone holding the old short link is then silently sent somewhere new.
Yes, but only an unedited one. Bitly's tool reference describes the delete tool as permanently deleting a short link and marks it unedited links only, matching the REST operation summary. A link whose destination or title has ever been changed cannot be deleted through the connector, so archiving is the practical alternative.
No, but your plan caps what the assistant can do. Bitly states every account has monthly limits on API requests, short links, custom back-halves and redirects, and that these apply across the API and the Bitly apps together. Exceeding them returns a 429 error, so a free account limits bulk work rather than blocking the connector.
Aggregated engagement data about the people who clicked your links: countries, cities, device type, operating system, referrers and referring domains, plus click and scan counts over time. Bitly reports these as grouped breakdowns rather than individual visitor records. The data still leaves Bitly for your AI provider, which governs retention under its own terms.
Your calls are probably using the wrong group. Bitly explains that a user's default API group may be the personal one created at signup rather than the organization group holding your custom domain and higher limits. Specify a group explicitly, or change the default group under Settings then Integrations in the Bitly web app.
Yes. Bitly documents two authentication methods: OAuth 2.1 with Dynamic Client Registration, which it recommends, and a static API token generated from your Bitly API settings and passed as a bearer header. Both reach the same endpoint. Bitly warns that access tokens are secret data and should never be exposed client-side.
No. Every domain tool in both the directory listing and Bitly's tool reference reads existing domains — listing what is available and returning custom link details. No tool registers, edits or removes a domain, and neither source documents any campaign object. Domain setup remains a DNS and web-app task outside the connector.
Sources
- Bitly MCP server documentation (retrieved 2026-08-21) · retrieved 2026-08-21
- Bitly MCP tools reference (retrieved 2026-08-21) · retrieved 2026-08-21
- Bitly MCP changelog (retrieved 2026-08-21) · retrieved 2026-08-21
- Bitly MCP configuration details (retrieved 2026-08-21) · retrieved 2026-08-21
- Bitly MCP usage examples (retrieved 2026-08-21) · retrieved 2026-08-21
- Bitly API rate limits (retrieved 2026-08-21) · retrieved 2026-08-21
- Bitly API troubleshooting and tips (retrieved 2026-08-21) · retrieved 2026-08-21
- Bitly OpenAPI 3.0 specification, v4.0.0 (retrieved 2026-08-21) · retrieved 2026-08-21
- Live OAuth posture check: anonymous
initializereturned 401 with awww-authenticatebearer challenge naminghttps://api-ssl.bitly.com/.well-known/oauth-protected-resource(2026-08-21) · retrieved 2026-08-21 - Anthropic Connectors Directory entry (snapshot 2026-08-16) · retrieved 2026-08-16
- Bitly support — · Privacy
Server Info
- Category
- Data & Research
- Developer
- Bitly
- Tools
- 27
- Domain
- api-ssl.bitly.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.
Similar MCP Servers for Data & Research
Adobe Customer Journey Analytics
by Adobe Customer Journey Analytics
Related Resources
Ready to connect Bitly?
Connect Bitly once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.