Common Issues

Authentication error

If you see an authentication error when trying to use MCP, check the following:

  • API key format: Make sure the key starts with fibbs_live_ and is complete (no extra spaces or missing characters)
  • Authorization header: The header must be exactly Authorization: Bearer YOUR_KEY with a space after "Bearer"
  • Revoked key: Check the API Keys page in Fibbler to make sure the key has not been revoked
  • Expired key: API keys can have an expiration date. Create a new key if yours has expired

Tool not returning data

If a tool returns empty results, it usually means one of:

  • No data for the time period: Try a wider date range. If you just connected, data may not have synced yet
  • Missing integration: Google Ads tools require the Google Ads add-on. Deal tools require a CRM to be connected. Ask for an account overview to see what is connected
  • No influenced deals: If no deals match the influence threshold for the time period, the tool will return zero results. Check your attribution model settings

Rate limit exceeded

If you hit a rate limit, wait 60 seconds for per-minute limits or until midnight UTC for daily limits. See Rate Limits & Usage for the specific thresholds.

Connection refused or timeout

If your AI tool cannot connect to the MCP server at all:

  • Check the URL: The endpoint is https://app.fibbler.co/mcp
  • Network issues: Make sure your network allows outbound HTTPS connections
  • Restart the client: Some AI tools need to be restarted after changing MCP configuration

The three Google Ads MCP tools (insights, campaign analytics, audience insights) are only available if you have the Google Ads add-on connected. Similarly, the channel overlap tool requires both LinkedIn and Google Ads to be active.

Wrong CRM data showing

If you have multiple CRMs connected, make sure your question specifies which CRM to use (e.g., "show me influenced deals from HubSpot"). If you do not specify, the tool will default to your primary CRM or ask you to choose.

Still stuck? Email support@fibbler.co with your API key prefix (the first 15 characters) and a description of the issue.