MCP Server
Connect LLM agents to GetMint — Content Studio and Insights over one Model Context Protocol endpoint
GetMint provides a single remote MCP server so LLM agents (Claude, Cursor, Windsurf, or any MCP-compatible client) can interact with your data directly. One endpoint exposes the full toolset — both Content Studio and Insights. Authenticate with the same API key you use for the REST API, or connect over OAuth from Claude.ai — no SDK install, no local process.
Base URL
https://mcp.getmint.ai/mcpUses the MCP Streamable HTTP transport (spec 2025-03-26).
Connect
Pick your client. Header-based clients send a Bearer mint_live_* key; Claude.ai connects over OAuth (no key to manage); ChatGPT supports either.
Settings → Connectors → Add custom connector, then paste the URL — there's no key field, Claude connects over OAuth:
https://mcp.getmint.ai/mcpClick Connect, sign in to GetMint, and approve the consent screen. See Authentication → OAuth for what's requested.
Settings → Connectors → Add custom connector, paste the URL, and pick either auth method — ChatGPT supports both:
https://mcp.getmint.ai/mcp- OAuth — select OAuth, then sign in to GetMint and approve the consent screen (no key to manage). Same flow as the Claude.ai connector.
- API key — select API key / header auth and supply
Authorization: Bearer mint_live_YOUR_KEY_HERE.
Either way the connector reaches the full toolset. See Authentication for scopes, rotation, and what OAuth requests.
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"getmint": {
"type": "http",
"url": "https://mcp.getmint.ai/mcp",
"headers": { "Authorization": "Bearer mint_live_YOUR_KEY_HERE" }
}
}
}Add to your project's .mcp.json (or ~/.claude.json under mcpServers for a user-level entry). The type: "http" field is required — without it Claude Code treats the entry as a stdio server and ignores url/headers.
{
"mcpServers": {
"getmint": {
"type": "http",
"url": "https://mcp.getmint.ai/mcp",
"headers": { "Authorization": "Bearer mint_live_YOUR_KEY_HERE" }
}
}
}Then restart Claude Code and run /mcp to confirm the server is connected.
Settings → MCP → Add Server:
{
"getmint": {
"url": "https://mcp.getmint.ai/mcp",
"headers": { "Authorization": "Bearer mint_live_YOUR_KEY_HERE" }
}
}curl -X POST https://mcp.getmint.ai/mcp \
-H "Authorization: Bearer mint_live_YOUR_KEY_HERE" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'Connecting over OAuth? (Claude.ai, or ChatGPT with OAuth selected) — you don't need an API key, just paste the URL above and click Connect.
Using a header-based client? (Claude Desktop, Claude Code, Cursor, Raw HTTP — or ChatGPT with API key auth) — generate an API key under Settings → API Keys (keys start with mint_live_ / mint_test_, 74 chars).
See Authentication for both methods, scopes, rotation, and rate limits.
Tool groups
Both groups are served by the single /mcp endpoint; these pages document the tools in each.
Content Studio
Create briefs and generate articles. Consumes generation credits.
Insights
Domain & topic analysis, brand sentiment, alignment, and visibility. Read-only.
Authentication
API key + OAuth setup, scopes, rotation, and rate limits.
Troubleshooting
Common errors and how to fix them.
Every MCP tool maps 1:1 to a REST endpoint. If you prefer direct HTTP, the same API key works at api.getmint.ai.