Skip to main content
The Content Ignite MCP server lets AI assistants such as Claude work with your Fusion data. Ask questions in plain English, such as “How did revenue compare week on week?” or “Which publishers have tags with errors?”, and the assistant looks up the answer in your account. You connect simply by signing in with your Fusion account. The server address is:

​
What it can do

  • Answer questions from your data. Reporting, publishers, tags, experiments, integrations and the rest of Fusion, limited to what your role can see.
  • Search our documentation. Ask how a feature works, or how to set something up.
  • Link you to the right page in Fusion. Answers include links to the relevant report or setting, and it can explain the page you’re looking at if you share its link.
  • Work across your organisations. See Switching organisations.
During the beta the MCP server can only read data. It can’t change settings, publishers, ad stacks etc, but this will be unlocked very soon.

​
Connect your AI assistant

Works on every Claude plan, including Free (which allows one custom connector). Once added, the connector is available in Claude on the web, the desktop app and the mobile apps.
1

Add the connector

In Claude, go to Customize > Connectors, click + Add, then Add custom connector.On a Team or Enterprise plan, an Owner adds it once for everyone instead: Organization settings > Connectors > Add > Custom > Web.
2

Enter the details

Name it Content Ignite and enter the server address, https://mcp.contentignite.com. Click Continue.Claude detects how the server signs in. Keep the settings it suggests, then click Add.
3

Sign in and approve

Click Connect and work through the sign-in screens (see Signing in step by step): confirm the connection, sign in to Fusion, choose the organisation to start in and the access to grant (see Security), and click Allow.On a Team or Enterprise plan, each member does this themselves from Customize > Connectors, so everyone connects with their own account.
4

Use it in a chat

Click + in the message box, then Connectors, and turn on Content Ignite. Then just ask.

​
Signing in step by step

Whichever assistant you use, connecting takes you through up to three screens:
1

Your assistant's own screen

Some assistants, including Claude, first ask you to confirm you want to connect. This screen belongs to the assistant, so it looks different in each one.
2

Application Access Request

A page on mcp.contentignite.com shows which application wants to connect, and where its access will be sent. Check both match the assistant you’re connecting:
  • Claude (web, desktop and mobile): https://claude.ai/api/mcp/auth_callback. It may also show Verified domain: claude.ai.
  • Claude Code, Cursor, VS Code and other apps on your computer: usually a localhost or 127.0.0.1 address.
If they match, click Allow Access. If you didn’t start the connection yourself, or don’t recognise the address, click Deny.
3

Sign in to Fusion and approve

Sign in if you aren’t already, choose the organisation to start in and the access to grant, then click Allow. You’re taken back to your assistant, ready to go.
The two approvals do different jobs. The first confirms which app gets the connection, so someone else’s app can’t pass itself off as yours. The second is where you decide what it can see and do.

​
Security and access

When you connect, Fusion shows which app is asking for access. You choose what to grant:
  • Your role still applies. The assistant can never see or do more than you can in Fusion.
  • No account changes. A connection can’t create or edit users, change passwords or roles, or create API tokens, whatever access it has.
  • One organisation at a time. Each connection only sees the organisation it’s working in.
  • You stay in control. See and disconnect your connected apps at any time in Fusion, under Account Preferences > Connected Apps. Disconnecting takes effect within a minute.
  • Connections expire. You’ll be asked to sign in again after 90 days, or sooner if you’re removed from the organisation.
Only connect AI assistants you trust, and remember that what you ask, and the data the assistant reads to answer, is shared with that assistant’s provider.

​
Switching organisations

If you have access to more than one organisation, the connection starts in the one you choose when you approve it. To work in another, just ask:
“Which organisation are you using?” “Switch to Beta Publishing.”
Every answer that uses your data says which organisation it came from. Switching only affects that one connection. The organisation you have selected in Fusion stays the same, and so do any other assistants you’ve connected.

​
Connecting with an API token

For assistants that can’t sign in with OAuth, you can send your personal API Access Token from your Fusion account page instead. In Claude, add it under Request headers when adding the connector, as Authorization: Bearer <token>.
An API token gives full access to everything your role allows, doesn’t expire, and always works in the organisation that was active when you copied it. Treat it like a password, and use sign-in instead wherever you can. If a token is exposed, click Revoke Token on your account page to replace it.

​
Troubleshooting

Sign-in links last 10 minutes and work once. Start the connection again from your assistant.
The first approval confirms which app is connecting, the second chooses the organisation and access it gets. See Signing in step by step.
During the beta, write access is restricted. This will be made available very soon.
You’ve been removed from the organisation the connection was working in. Ask the assistant to switch to another organisation, or reconnect.
Check the connection is still listed under Account Preferences > Connected Apps in Fusion. If it isn’t there, it was disconnected or expired: reconnect from your assistant. If it is, contact your account manager.