Provider REST API

16 actions

Connect Claude to Bitly

Shorten and manage links and QR codes, and read their click analytics. Toolspoke puts 16 of its actions behind one MCP endpoint that Claude, Cursor, and Codex all speak.

Connect View pricing

Connection: Provider REST API
Authentication: Access token
Actions exposed: 16
What a call bills: Nothing
Adapter: Maintained by Toolspoke

Connected in three steps

1
Install Bitly
Open the marketplace in your workspace, add Bitly to the project your agents work in, and it appears on the gateway immediately.
2
Connect the credential
Authenticate with access token. Where to get one, and what it has to be able to reach, is the next section.
3
Point your agent at the gateway
Give your client one address, https://toolspoke.com/mcp. Claude Code takes it as a command, Claude and Claude Desktop add it as a custom connector, and Cursor, Codex and VS Code each read it from a config file of their own.

.mcp.json

{
  "mcpServers": {
    "toolspoke": {
      "type": "http",
      "url": "https://toolspoke.com/mcp"
    }
  }
}

One block covers every tool you have installed. Bitly shows up in the client as soon as your policy allows it, and so does everything else you install later.

Where the address goes, per client

Claude Code: Run it in your project, then /mcp to sign in
claude mcp add --transport http toolspoke https://toolspoke.com/mcp
Claude and Claude Desktop: Settings, then Connectors, then Add custom connector
https://toolspoke.com/mcp
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json for one project
{ "mcpServers": { "toolspoke": { "url": "https://toolspoke.com/mcp" } } }
Codex: ~/.codex/config.toml
[mcp_servers.toolspoke] url = "https://toolspoke.com/mcp"
VS Code: .vscode/mcp.json, or the MCP: Add Server command
{ "servers": { "toolspoke": { "type": "http", "url": "https://toolspoke.com/mcp" } } }

What Bitly asks for

Access token. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

Access tokenRequired: Bitly → Settings → Developer settings → API → enter your password → Generate token. The token acts as you, in every group you belong to.

What Claude can do in Bitly

16 actions, each one declared and named by the connector rather than discovered at runtime. A workspace policy grants a person all of them, a hand-picked selection, everything on the read side, everything on the write side, or none.

Reads: 12Reads
Writes: 3Writes
Destructive: 1Destructive

Reads

Fetches data and changes nothing.

get_user
The user this token belongs to, with their default group guid.
list_groups
The groups this token can reach, each with the group_guid most other calls need. Reads real account data, so an install tests itself with it.
get_bitlink
One Bitlink's details - destination, title, tags, created date and archived state.
expand_bitlink
Return the long URL a Bitlink points to.
list_group_bitlinks
The Bitlinks in one group, newest first, optionally searched or filtered to archived links.
get_clicks
Click counts for one Bitlink, bucketed by time unit.
get_clicks_summary
Total clicks on one Bitlink over a window.
get_click_countries
One Bitlink's clicks broken down by country.
get_click_referrers
One Bitlink's clicks broken down by referrer.
get_group_clicks
Click counts across every Bitlink in a group, bucketed by time unit.
get_qr_code
One QR code's details - title, destination and archived state.
list_group_qr_codes
The QR codes in one group.

Writes

Creates or updates something on the other side.

shorten
Shorten a long URL into a Bitlink. Returns the existing Bitlink when this URL was already shortened in the group. Counts against the plan's monthly link limit.
create_bitlink
Create a Bitlink with a title and tags in one call. Use shorten when a bare short link is enough.
update_bitlink
Change a Bitlink's title or tags, or archive it. Does not change where the link points - redirecting a link everyone has already shared is deliberately not offered here.

Destructive

Deletes or permanently alters something. Worth granting on purpose.

delete_bitlink
Delete a Bitlink. Destructive because it cannot be undone and anyone holding the short link stops reaching the destination.

What it will not do

Enforced by the gateway rather than left to convention, which is why each of these can be stated flatly.

It cannot call anything else: The 16 actions above are the whole of it. A call to any other name is refused before it reaches Bitly rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time.
It reaches no further than your credential: Toolspoke holds no access to Bitly of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either.
It never hears from Bitly: Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Bitly. An agent has to ask.
It does not smooth over provider limits: Toolspoke does not retry, queue or back off around Bitly's own rate limits. A call that Bitly refuses comes back to the agent as a failed call.

Before you connect it

What can Claude do in Bitly?

16 named actions: 12 that only read, 3 that write and 1 that delete or permanently alter something. They include get_user, list_groups and shorten. Nothing outside that list is reachable: the connector declares each operation by name rather than proxying whatever an agent asks for.

What credentials does the Bitly connector need?

Access token. The connector asks for access token. Values are encrypted at rest and attached to the outbound request by the gateway, so they are never part of the arguments an agent sends and never reach the audit log.

Does the Bitly connector work with Cursor and Codex, or only Claude?

Any client that speaks MCP, and every one of them gets the same 16 actions. There is a single address, https://toolspoke.com/mcp. Claude Code adds it with claude mcp add --transport http, Claude and Claude Desktop take it as a custom connector in settings, Cursor reads it from .cursor/mcp.json, Codex from ~/.codex/config.toml, and VS Code from .vscode/mcp.json. Each of them signs in to the gateway itself, so there is no key to paste.

What does the Bitly connector not do?

The 16 actions above are the whole of it. A call to any other name is refused before it reaches Bitly rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time. Toolspoke holds no access to Bitly of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either. Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Bitly. An agent has to ask. Toolspoke does not retry, queue or back off around Bitly's own rate limits. A call that Bitly refuses comes back to the agent as a failed call.

Can I limit which actions an agent can call?

Yes, in two places. The project switches Bitly's actions on and off one at a time, for everyone in the project at once, and the screen groups them by read, write and destructive so turning off everything that deletes is one click. An individual agent key can then be narrowed further, to particular toolkits in a project and to particular actions in a toolkit. Whatever it was granted, a key never reaches a project its owner cannot.

What gets recorded when an agent calls Bitly?

Every attempt, with the agent that made it and the person that agent belongs to, the full request payload, the response payload, the status, the duration, and what the call cost in sandbox time and model tokens. Values whose key names a secret are masked out before the record is shown to anyone. An operation the connector marks as not retained never has its response body written at all, so the gateway keeps no second copy of what was read.

More marketing connectors

Browse all of them