MCP Server
Connect LLM agents to GetMint — Insights and Content Studio over one Model Context Protocol endpoint
The GetMint MCP server is a thin gateway over the REST API — every tool maps 1:1 to an endpoint, reshaping the same data your dashboard shows so an LLM can call it with no HTTP glue. One remote endpoint exposes the full surface: 13 Insights tools read-only analytics and 9 Content Studio tools (the brief → article flow).
Base URL
https://mcp.getmint.ai/mcpStreamable HTTP transport (MCP spec 2025-03-26). See Connect your client for per-client setup.
Authentication at a glance
Authenticate with the same API key you use for the REST API — pass it as Authorization: Bearer mint_live_* (the X-API-Key header also works). Claude.ai and ChatGPT can connect over OAuth instead, with no key to manage. Full details on scopes, rotation, and rate limits are on Authentication.
MCP calls share the REST rate limit: 200 req/min per key. A tool call is typically one API request, so MCP does not multiply your budget.
How the tools work together
Agents usually move through three phases — discover which domain and topic to look at, analyze it, then optionally act by producing content. IDs flow forward: list_domains gives a domainId, list_topics gives a topicId, and create_brief gives a briefId you poll and finalize before generation.
Explore
Connect your client
Claude.ai, ChatGPT, Claude Desktop, Claude Code, Cursor, or raw HTTP — paste the URL and go.
Capabilities
Every tool grouped by job, credit and safety annotations, and known limitations.
Insights tools
Domain & topic analysis, brand sentiment, alignment, citations, and shopping. Read-only.
Content Studio tools
Create briefs and generate articles. Consumes generation credits.
Authentication
API key + OAuth setup, scopes, rotation, and rate limits.
Troubleshooting
Common errors and how to fix them.
Prefer direct HTTP? The same API key works at api.getmint.ai, and the Cookbook has task-first REST recipes with full date control.