BrandJet AI
    HomePricing
    Contact us
    Get Started
    Quickstart
    Email Outreach
    Email Infrastructure
    Connect Email Accounts
    Campaigns & Sequences
    Deliverability & Analytics
    Social & Multichannel
    Connect Social Channels
    Multichannel Campaigns
    Leads
    Find & Enrich Leads
    Import & Manage Lists
    Recurring Lead Collection
    Billing & Workspace
    Plans, Trials & Limits
    AppSumo, BYOK & Upgrades
    Workspace, Team & Account
    Replies & Unibox
    Unibox & Snippets
    Workflows
    Workflow Builder
    Lifecycle Sequences
    Artemis (AI Assistant)
    Getting Started with Artemis
    Troubleshooting Artemis
    Integrations & Developers
    MCP Server
    Connect the MCP server to Claude or ChatGPTFix MCP authorization errors and tier gating
    REST API & Webhooks
    CRM Integrations
    Slack, Discord & Notifications
    Monitoring & Intelligence
    Mentions
    Competitor & Social Tracking
    Content Feed & Website Analytics
    AI / LLM Monitoring
    Press & PR Tools
    Press Outreach
    AI Agents
    Agent Types & Setup
    Help Center/Integrations & Developers/MCP Server

    5 min read

    Fix MCP authorization errors and tier gating

    If the BrandJet MCP server returns an authorization error or you cannot see expected tools, walk through these checks. Most issues come down to a token problem, a tier restriction, or a workspace mismatch.

    Authorization with the MCP server failed with an ofid_ reference

    The ofid_ code is an internal request ID we use to look up exactly which check failed. Share it in a support ticket if needed.

    Step 1 — Verify the token

    • Open Settings → API and MCP.

    • Confirm the token you are using is listed and active (not revoked).

    • If you cannot see it, generate a new one and update your client config.

    Step 2 — Confirm the right workspace

    Each MCP token belongs to one workspace. If you switched workspaces in the BrandJet UI but kept using an old token in Claude or ChatGPT, the requests fail because the token does not have access to the new workspace data.

    • Generate a new token from inside the workspace you want MCP to act on.

    • Replace it in your client config.

    Step 3 — Check plan eligibility

    The MCP server is available on Pro and above (SaaS) and AppSumo Tier 1+. Free plan tokens generate but always fail authorization at the server.

    • Open Settings → Billing → Plan to confirm your tier.

    • Upgrade if you are on Free, then generate a fresh token.

    Step 4 — Restart the client

    Claude Desktop and ChatGPT cache MCP connections. After updating config, restart the client completely so it re-handshakes with the server.

    Are tools gated by tier?

    All read tools (list campaigns, get leads, search mentions, analytics queries) are available at every tier with MCP access.

    Write tools (create campaign, launch campaign, enrich leads, send message) are also available at every tier with MCP access, but they consume the same plan resources as the equivalent UI action:

    • leads.enrich uses enrichment credits.

    • campaigns.launch consumes from your monthly send quota.

    • leads.create counts against your lead allowance.

    • mcp.bulk_* tools are subject to per-minute rate limits proportional to your tier.

    So a Tier 1 user can call leads.enrich, but the lookup fails if enrichment credits are exhausted, the same way it would fail in the UI.

    Tool not found

    If a tool you expect is missing from the client tool list:

    • Your client is using a stale tool manifest. Restart Claude Desktop or refresh ChatGPT MCP integration.

    • The tool is beta-only. Some new tools require a feature flag; open a ticket to request access.

    • You are on the Free plan; the MCP server returns an empty tool list for unauthorised tiers.

    Rate limited

    Each tier has a per-minute MCP call budget to keep the server stable across customers. If you hit it, the response includes a retry-after header. AI clients usually respect it automatically.

    Token best practices

    • Use one token per device or per AI client; do not share.

    • Rotate tokens every 90 days or whenever you change devices.

    • Revoke tokens you no longer use from Settings → API and MCP.

    Still stuck?

    Open a support ticket with the full ofid_ reference and the client you are using (Claude Desktop, ChatGPT, Cursor, etc.). We can look up the exact denial reason on our side.