Getting Started with MCP

Fibbler's MCP (Model Context Protocol) lets you connect your attribution data to Claude, ChatGPT, Cursor, and other LLMs. Ask questions about pipeline, revenue, campaigns, and deal attribution in natural language and get answers directly from your Fibbler data.

MCP is included on the Unlimited and Agency plans. See pricing for details.

What is MCP?

The Model Context Protocol is an open standard that lets LLMs connect to external data sources. When you connect Fibbler via MCP, Claude or ChatGPT can pull campaign performance, deal attribution, customer journeys, and more directly from your Fibbler account. No copy-pasting, no screenshots, no exporting CSVs.

What you can do

With MCP connected, you can ask things like:

  • "Which campaigns influenced the most pipeline this quarter?"
  • "Show me the customer journey for Acme Corp"
  • "How did our LinkedIn Ads performance change compared to last month?"
  • "What is our ROAS on Google Ads?"
  • "Which companies are engaging with our ads but don't have a deal yet?"

See Available Tools for the full list of data you can access.

Prerequisites

  • An active Fibbler subscription (Unlimited or Agency plan)
  • A connected CRM (HubSpot, Salesforce, or Attio)
  • Claude, ChatGPT, Cursor, Claude Code, or any MCP-compatible tool

Claude (web)

Uses OAuth. No API key needed.

  1. Go to claude.ai/settings/connectors and click Add connector
  2. Paste the server URL: https://app.fibbler.co/mcp
  3. Log in with your Fibbler account when prompted to authorize
  4. Start a new chat and ask a question about your data

ChatGPT

Uses OAuth. No API key needed.

  1. Open ChatGPT and start a new conversation
  2. Click the connectors icon (plug icon) in the message input
  3. Select Add MCP Server
  4. Paste the server URL: https://app.fibbler.co/mcp
  5. Log in with your Fibbler account when prompted to authorize

Claude Desktop

Requires an API key.

  1. Open Claude Desktop and go to Settings → Developer → Edit Config
  2. This opens your claude_desktop_config.json file
  3. Add the following to the mcpServers section:
{
  "mcpServers": {
    "fibbler": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://app.fibbler.co/mcp",
        "--header",
        "Authorization: Bearer YOUR_API_KEY"
      ]
    }
  }
}
  1. Replace YOUR_API_KEY with your actual API key
  2. Save the file and restart Claude Desktop

You should see Fibbler listed as a connected tool in the bottom-left of a new conversation.

Cursor

Requires an API key.

  1. Open Cursor and go to Settings → MCP
  2. Click Add new MCP server
  3. Set the transport type to SSE
  4. Enter the Fibbler MCP URL: https://app.fibbler.co/mcp
  5. Add the authentication header: Authorization: Bearer YOUR_API_KEY

Claude Code

Requires an API key. Run the following command in your terminal:

claude mcp add fibbler \
  --transport http \
  --url https://app.fibbler.co/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

Replace YOUR_API_KEY with your actual API key. Fibbler will be available in all future Claude Code sessions.

Verify the connection

Once connected, try asking something simple like "Give me an overview of my Fibbler account" or "What data sources do I have connected?". If the connection is working, you will get a response with your account details.

If you get an authentication error, double-check that your API key is correct and has not been revoked (for API key connections), or try disconnecting and reconnecting (for OAuth connections). See Common Issues for troubleshooting.

API keys

Claude Desktop, Cursor, and Claude Code require an API key to connect. You can create and manage API keys from the MCP page in your Fibbler settings.

  1. Go to Settings → MCP and scroll to the API Keys section
  2. Click Create API Key
  3. Give the key a name (e.g., "Claude Desktop" or "Cursor")
  4. Copy the key immediately. It starts with fibbs_live_ and is only shown once.
Store your API key somewhere safe. You will not be able to see it again after leaving the page. If you lose it, revoke the old key and create a new one.

You can create multiple API keys for different tools. Each key can be named and revoked independently. Only account Owners and Admins can create and revoke API keys.