MCP for AI agents

What this is

A hosted Model Context Protocol server so Cursor, Claude, and other MCP clients can create short links, read analytics, and manage campaigns in your workspace using an API key.

MCP does not call the platform AI provider. The client’s model is the one that talks. Usage counts against API rate limits, not the in-app AI message quota.

Before you start

• Developer API must be available on your plan.
• You are a workspace owner (to create an API key).
• Copy a workspace API key from Settings → Developer API. Production keys start with lc_live_.

Connect

Use streamable HTTP. This Cursor-compatible snippet is the primary config — replace the origin and key:

{
  "mcpServers": {
    "Linkchime": {
      "type": "http",
      "url": "https://YOUR_HOST/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Claude Code and Claude Desktop accept the same url and headers without type.

Clients that speak Bearer HTTP MCP can use the same URL and API key. ChatGPT custom connectors that require OAuth are not supported.

Use a workspace API key. A logged-in browser session is not accepted.

You can also send the key as X-Api-Key.

What it can do

• Search, get, create, and update short links
• Create up to 50 links at once
• Mark a link as a QR code
• Read workspace and link analytics
• List campaigns and campaign analytics
• List and get landing pages

Writes run immediately (same as the REST API). Passwords, billing, admin, and API-key management are not exposed.

Related pages

• Developer API
• AI assistant
• Usage limits