MCP Server
Connect Claude Code or any MCP client so your AI agent can work inside your studio.
What It Is
GameTrowel ships an official MCP (Model Context Protocol) server at https://mcp.gametrowel.com/mcp, available on the Studio plan. Connect Claude Code — or any MCP client that supports HTTP transport with custom headers — and your AI agent gets 59 tools spanning every module: it can list your games, triage and answer support tickets, build and publish landing pages, draft devlogs, review key requests, check analytics, and keep your launch timeline moving, all from a conversation.
Generate an API Key
- Go to Dashboard → Studio Settings → API Keys
- Click "Generate Key" and give it a name
- Copy the key and store it somewhere safe
Connect from Claude Code
Add the server with one command, substituting your API key:
claude mcp add --transport http gametrowel https://mcp.gametrowel.com/mcp --header "Authorization: Bearer YOUR_API_KEY"Then ask Claude to "list my games" to confirm the connection works.
Other MCP Clients
Any MCP client that supports HTTP transport and custom headers can connect — including Claude API/SDK agents and Cursor. For clients configured via JSON:
{
"mcpServers": {
"gametrowel": {
"url": "https://mcp.gametrowel.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}What Your Agent Can Do
| Module | What the tools cover |
|---|---|
| Games | List games, read details, update metadata |
| Landing Pages | Edit sections, run the async AI design pipeline, publish |
| Support | List, triage, and reply to tickets, with AI-drafted replies |
| Blog | Draft, edit, schedule, and publish devlogs |
| Press Kit | Read and update press kit content and fact sheets |
| Mailing List | View subscribers and draft campaigns |
| Key Requests | Review requests and resolve them with a key |
| Smart Links | Create and update smart links, read click stats |
| Monitoring | Read coverage items and sentiment |
| Social | Draft, schedule, and publish social posts |
| Steam | Read Steam analytics and market data |
| Timeline | Read and update launch timeline tasks |
| Analytics | Query unified metrics across all modules |
| Help Center | Create and update categories and articles |
| Localization | Trigger and review automatic translations |
reply_to_ticket, publish_social_post, and resolve_key_request. They carry MCP "destructive" annotations, so well-behaved clients ask for your approval before calling them. Mailing campaigns are draft-only by design — sending always happens from the dashboard — and press outreach is not exposed through the MCP server at all.Safety & Permissions
- Server-side enforcement — every call runs the same tier, role, and ownership checks as the dashboard. An API key can never do more than the studio it belongs to.
- Zero delete operations — the server exposes no tools that delete data.
- Rate limits — requests are rate limited per key to keep a runaway agent contained.
- Instant revocation — revoke a key in Studio Settings and it stops working immediately.
Troubleshooting
| Status | Meaning | Fix |
|---|---|---|
| 401 | Invalid or revoked API key | Generate a new key in Studio Settings and update your client config |
| 403 | Plan or role restriction | The MCP server requires the Studio plan; some tools also need a role with access to that module |
| 404 | Wrong game ID | Call list_games first and use the IDs it returns |
| 429 | Rate limited or reply cap reached | Slow down request frequency and retry after a short wait |