Bitly MCP

Live

API KEY

LINK MANAGEMENT

Marketing

Every shortened link, campaign tag, and click analytics record your team manages lives in Bitly. Bitly MCP gives your agent authenticated access to link data scoped to the user who authorized it.

  • Acts as the user: Access and write actions stay tied to the Bitly MCP account that authorized the agent.
  • Credentials stay vaulted: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: User permissions enforced. 90-day audit trail.
Bitly MCP
agent · Acme Q3
Run
Which of our campaign links got the most clicks this week and what were the top referrers?
S
bitly_link_stats
72ms
Link management agent
Top 3 this week: Q4-launch-email (4,820 clicks, top referrers: email 78%, LinkedIn 12%), pricing-page-cta (3,110, direct 65%, Twitter 22%), webinar-reg (2,480, email 82%, Slack 11%).
Sources: 3 campaign links, this week
bitlymcpmcp
3 links
18:29
Message Claude...

Tools your link management agent reaches for on Bitly MCP, scoped per user.

CALL ANY TOOL
Shorten URLs, retrieve click stats, list and update links, and analyze referrer and geo breakdowns.
bitly_link_shorten
Shorten URL
Shorten a long URL using the authenticated Bitly account.
Parameters
Name
Type
Required
Description
long_url
string
Required
URL to shorten
domain
string
Optional
Custom domain (if configured)
title
string
Optional
Link title
bitly_link_stats
Get link stats
bitly_links_list
List links
bitly_link_update
Update link
bitly_link_clicks
Get click breakdown
Build your Agent
Drop the toolkit in, point it at the user, and your link management agent can use Bitly MCP from the first run.
import { ScalekitClient } from "@scalekit-sdk/node";
import { DynamicStructuredTool } from "@langchain/core/tools";
import { createReactAgent } from "@langchain/langgraph/prebuilt";
import { z } from "zod";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["bitlymcp"], toolNames: ["bitly_link_shorten", "bitly_link_stats", "bitly_links_list"] },
pageSize: 100,
});

const lcTools = tools.map((t) => new DynamicStructuredTool({
name: t.tool.definition.name,
description: t.tool.definition.description,
schema: z.object({}).passthrough(),
func: async (args) => {
const { data } = await sk.tools.executeTool({
toolName: t.tool.definition.name,
identifier: "user_123",
params: args,
});
return JSON.stringify(data);
},
}));

const agent = createReactAgent({ llm, tools: lcTools });
import { ScalekitClient } from "@scalekit-sdk/node";
import OpenAI from "openai";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["bitlymcp"], toolNames: ["bitly_link_shorten", "bitly_link_stats", "bitly_links_list"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
type: "function",
function: {
name: t.tool.definition.name,
description: t.tool.definition.description,
parameters: t.tool.definition.input_schema,
},
}));

const resp = await openai.responses.create({
model: "gpt-4o", input: prompt, tools: llmTools,
});
import { ScalekitClient } from "@scalekit-sdk/node";
import Anthropic from "@anthropic-ai/sdk";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["bitlymcp"], toolNames: ["bitly_link_shorten", "bitly_link_stats", "bitly_links_list"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
name: t.tool.definition.name,
description: t.tool.definition.description,
input_schema: t.tool.definition.input_schema,
}));

const msg = await anthropic.messages.create({
model: "claude-sonnet-4-6", max_tokens: 1024,
tools: llmTools,
messages: [{ role: "user", content: prompt }],
});
import { Agent } from "@google/adk/agents";
import {
MCPToolset, StreamableHTTPConnectionParams,
} from "@google/adk/tools/mcp";

const toolset = new MCPToolset({
connectionParams: new StreamableHTTPConnectionParams({
url: "https://mcp.scalekit.com/bitlymcp",
headers: { Authorization: `Bearer ${userScopedToken}` },
}),
});

const agent = new Agent({
name: "agent", model: "gemini-2.0-flash",
tools: await toolset.getTools(),
});
Try these prompts
Paste any prompt into your agent to start using Bitly MCP.
Links & stats
Copy the prompt
Copied
List all links created this week.
Copy the prompt
Copied
Get click stats for [bitlink] last 7 days.
Copy the prompt
Copied
Which links had the most clicks this month?
Copy the prompt
Copied
Show referrer breakdown for [link].
Action & management
Copy the prompt
Copied
Shorten [URL].
Copy the prompt
Copied
Update the title of [bitlink] to [title].
Copy the prompt
Copied
Add tag [campaign] to [bitlink].
Copy the prompt
Copied
Change destination URL of [link] to [new URL].
Reporting
Copy the prompt
Copied
Total clicks across all campaign links this month.
Copy the prompt
Copied
Top 5 links by click count.
Copy the prompt
Copied
Click trend for [link] last 30 days.
Copy the prompt
Copied
Which links drove traffic from LinkedIn?
SEE HOW AUTH WORKS
Users authorize Bitly MCP once. Their credentials stay vaulted, every call is checked, and every action is logged.
1
Authorize
Your user connects
Bitly MCP
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Bitly MCP
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Bitly MCP
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Bitly MCP
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
Same per-user auth pattern across other link management agents and MCP connectors. Working code, live demos, fork what fits.
SALES
Outbound prospecting agent
Build targeted prospect lists with Apollo, enrich with firmographic data, and draft personalised outreach. Runs on a schedule.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Other connector libraries treat auth as a demo afterthought. Scalekit starts with user identity, scope enforcement, and audit.
01.
Shared tokens break per-user analytics
A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential so attribution, audit, and scope stay accurate.
// shared token
 audit → bot_service_account
 user_filter → broken

 // scalekit
 audit → user_abc
 scope → enforced ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
Bitly MCP today. Others tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions
Does the agent access Bitly MCP as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.
Where is the Bitly MCP api key stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.
Can I limit what the agent is allowed to do in Bitly MCP?
Yes. Pass a tool name filter to listScopedTools so the link management agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Bitly MCP.
What happens when a user revokes Bitly MCP access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.
Can the agent access links created by other members of the Bitly organization?
Only links the authorizing user's API key has access to. Organization-level visibility depends on the user's Bitly role. Links in other groups require the user to have group membership.
Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""bitlymcp"": {
""url"": ""https://mcp.scalekit.com/bitlymcp"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.bitlymcp]
url = ""https://mcp.scalekit.com/bitlymcp""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""bitlymcp"": {
""url"": ""https://mcp.scalekit.com/bitlymcp"",
""type"": ""http""
}
}
}