What is this?
The Platform MCP server (/api/platform/v1/mcp) is a second MCP endpoint aimed at platform owners and superadmins. Where the Workspace MCP connects an AI assistant to one channel’s inbox and contacts, the Platform MCP connects it to your platform-level operations: reading and working support tickets, looking up users, browsing plans and add-ons, and checking subscription status — across your whole platform, with no channel required.
The Platform MCP tab appears in the Developer Portal’s MCP section only for platform owners and superadmins. Workspace staff cannot see or use it.
Server details
What can I do here?
- Read, triage, and reply to support tickets
- Add internal notes to tickets that only your team can see
- Assign tickets to team members, change status
- Look up platform users by name, email, or phone
- Check a user’s active subscriptions and the plans or add-ons they are on
- Browse the plans and add-ons you sell
How to use it
1
Get your API key
Open Developer → API Keys and generate or copy your key. The key owner must be a platform owner or superadmin — a workspace-only key returns
403.2
Connect your client
Use the setup snippet from the Developer Portal’s MCP → Platform MCP tab, or copy one of the examples below. Replace Then run
<API_KEY> with your key.- Claude Code
- Claude Desktop
- Cursor / VS Code
- Other
/mcp inside Claude Code to confirm the connection.3
Ask your assistant
Once connected, ask in plain language. For example:
- “Show me the open support tickets, oldest first.”
- “Add an internal note to ticket #42 saying the refund is pending.”
- “Assign all unassigned tickets from today to me.”
- “Which users are on the Pro plan?”
- “Look up the user john@example.com and show their subscription.”
How it stays safe
- Only platform owners and superadmins can connect. Role and platform membership are checked again on every call.
- Every call stays inside your own platform. There is no way to query another platform’s data.
- Every change (reply, note, assignment, status change) is recorded in the activity log with the tool, the outcome, and the key version.
- Users, subscriptions, and add-ons are read-only here. Changing user plans, deleting tickets, creating tickets on behalf of users, and posting as the customer stay in the dashboard.
- Your client asks you to approve every write before it runs.
Troubleshooting
403on every call. The key owner needs the platform owner or superadmin role. Workspace-level keys are not accepted.- A tool doesn’t appear. The Platform MCP only exposes tools for tickets, users, subscriptions, and plans. If you need workspace tools (contacts, inbox, automations), use the Workspace MCP.