Skip to main content

​
Connect your assistant to Whathead MCP

Every MCP client uses the same Whathead endpoint: 
https://www.whathead.com/mcp
The main difference is how the client signs in.

​
Which client should you use?

Claude

Best for live day-to-day work when a person is actively asking questions, checking campaigns, and reviewing performance.

ChatGPT

Best when your team wants the same live workspace access inside ChatGPT. Just make sure the connector is enabled in the actual conversation.

Manus

Best for stable, longer-running sessions where a connector token is usually a better fit than browser sign-in.

n8n

Best for recurring workflows, exports, and internal automations that should keep using the same named token.

​
Two access styles

Best for human-led use in Claude and ChatGPT.Choose this when:
  • a person is actively working inside the AI client
  • you want the simplest sign-in flow
  • you want normal workspace access rules to apply automatically

​
Claude

1

Add the Whathead MCP endpoint

Paste https://www.whathead.com/mcp into Claude’s MCP setup.
2

Sign in with Whathead

Complete the Whathead sign-in flow in the browser popup.
3

Start using your workspace

Claude can now work with the accounts, assets, reporting, and campaign data already available in Whathead.

​
ChatGPT

1

Use the same endpoint

Add https://www.whathead.com/mcp in ChatGPT’s MCP setup.
2

Complete the Whathead login

Approve access through the normal sign-in popup.
3

Enable the connector in the chat

If ChatGPT says MCP is unavailable, the connector is usually not selected inside that conversation yet.

​
Manus and n8n

For automation tools, most teams prefer a connector token.
1

Open the MCP page in Whathead

Create a token with a clear name such as manus-reporting or n8n-exports.
2

Scope it if needed

Limit the token to the platforms, accounts, or actions you actually want that workflow to use.
3

Use it against the same endpoint

Send the token as a Bearer token to https://www.whathead.com/mcp.

​
What access depends on

MCP access is not separate from your workspace. It follows the same Whathead access model. That means:
  • the workspace needs active access
  • the platform should already be connected in Whathead
  • the relevant account should already be available to the workspace
  • connector tokens can be narrower than full workspace access

​
Good setup habits

Create separate connector tokens for separate jobs instead of one shared token for everything. For example: one for reporting, one for exports, and one for QA or publishing support.
If your team mostly works in Claude or ChatGPT, start with normal sign-in first. Move to connector tokens when you have a stable recurring workflow that needs it.

​
If setup does not work

The most common reasons are:
  • the workspace does not currently have active access
  • the platform is not connected yet
  • the account is not available to that workspace
  • the token or connector is more limited than expected

Go to troubleshooting

Use the connection troubleshooting guide if MCP setup or account visibility is not behaving as expected.

See real workflows

Learn how teams actually use MCP once setup is complete.