Skip to main content
Once you’ve minted a key, point any MCP-aware client at the Mesh Pilot server. Every client uses the same endpoint and bearer key.
Connect your platforms (Meta, Amazon, etc.) under Settings → Integrations before connecting a client. The MCP server acts on those cockpit connections; your AI client never sees platform credentials.

​
Claude Code

​
Claude Desktop / Cursor / generic MCP config

Most clients accept a JSON server entry:

​
Gemini CLI, ChatGPT, and others

Any client that supports a remote/streamable-HTTP MCP server works: give it the URL https://mcp.meshpilot.app/mcp and the Authorization: Bearer header with your key.

​
Verify the connection

Ask your client to list what it can do, or call the whoami tool — it returns the brands, platforms, access mode, and limits your key resolves to. If whoami shows the expected ceiling, you’re connected.

​
Try it

  • “Audit my Ayurpet Meta account.”
  • “Show me approval-pending actions.”
  • “Approve the scale on campaign 9234 and reject the rest.”
Write actions land in your Inbox as proposals (unless an autonomy threshold lets them auto-run), and everything is recorded in the audit log.

​
Troubleshooting

  • 401 / unauthorized — the key is wrong, revoked, or expired. Mint a fresh one in Settings → MCP.
  • “No credentials for brand …” — the platform isn’t connected for that brand, or needs reconnect. Fix it under Settings → Integrations.
  • Calls refused (denied) — the key’s scope excludes that brand/platform, it’s read-only attempting a write, or it hit its daily rate limit. Check scopes & roles.

Manage your keys

Settings → MCP.