Adobe Customer Journey Analytics
Run cross-channel reports and build segments in Adobe Customer Journey Analytics.
Shorten links, build QR Codes and read click analytics.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Bitly MCP server connects Bitly link shortening to Claude, ChatGPT or any MCP-compatible agent. It creates short links and QR Codes, reads click and scan analytics, and lists workspace links and domains. It also edits links that already exist — including their destination — so an assistant can silently retarget a short link people are already sharing.
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
INVALID_ARG_DOMAIN error when a group lacks access to the domain requested.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.
initialize returned 401 with a www-authenticate bearer challenge naming https://api-ssl.bitly.com/.well-known/oauth-protected-resource (2026-08-21) · retrieved 2026-08-21Connect Bitly once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.