Connect the Mintlify MCP server to Unblocked to give AI agents live documentation site context

Product documentation drifts from the code it describes: an endpoint changes in a pull request, and the Mintlify page explaining it stays the same until someone notices. Mintlify’s MCP server exposes your documentation project — page content, navigation, comments, and analytics — to AI agents, and Unblocked connects to it once so every agent can check what your docs say without its own Mintlify setup.

This is a third-party MCP server: Mintlify hosts and maintains it, and Unblocked connects to it as a verified MCP server. Nothing is ingested or indexed — Unblocked calls the read-only tools you select at the moment a question needs them, so answers reflect your documentation as it is now, on the branch you ask about.

Wiring Mintlify’s MCP server straight into an agent gives it raw pages and search hits. Unblocked’s Context Engine reasons across those results and your other sources — following a documented parameter to the pull request that renamed it, the Slack thread that agreed the change, and the open comment asking for the page to be updated — and returns one cited answer.

Once connected, any MCP-compatible coding agent — Claude Code, Cursor, Devin, GitHub Copilot, Codex — reaches Mintlify context through a single Unblocked MCP server connection.

What you get

• Live docs content and structure — Agents read the full MDX of any page, search across pages, and walk your navigation tree as it stands on the deploy branch or another branch.
• One connection for every agent — Connect Mintlify to Unblocked once. Claude Code, Cursor, Codex, and GitHub Copilot reach it through the Unblocked MCP server, with no per-agent Mintlify sign-in.
• No edits, publishes, or config changes — Mintlify’s server can also edit pages, change configuration, and publish. Unblocked offers only its read-only tools, and you choose which of them it may call from Settings → Data Sources.
• Docs checked against the code — The Context Engine reconciles Mintlify pages with your code, pull requests, and conversations, so an outdated page is flagged alongside the change that made it outdated — with citations.

Prerequisites

• An Unblocked account (free to start).
• A Mintlify account with access to the documentation project you want to query, and permission to authorize access to it.
• An MCP-compatible coding agent (Claude Code, Cursor, Devin, etc.) to use the context in your editor.

Step 1: Connect Mintlify to Unblocked

1. In Unblocked, go to Settings → Data Sources → Connect another data source, and under Documentation select Mintlify.
2. The Mintlify MCP server URL is filled in for you. Choose OAuth, click Connect, and sign in to Mintlify to authorize Unblocked.
3. Once Unblocked discovers the server’s tools, select the read-only tools it may use and click Save Settings.

Step 2: Install the Unblocked MCP server

On macOS or Linux, one command auto-detects and configures the supported agents on your machine:

On Windows, or when you prefer remote MCP, add the server manually using the configuration below, or follow the manual install guide .

claude mcp add -s user --transport http unblocked https://getunblocked.com/api/mcpsse

{
  "mcpServers": {
    "unblocked": {
      "url": "https://getunblocked.com/api/mcpsse"
    }
  }
}

https://getunblocked.com/api/mcpsse

Mintlify hosts and maintains this MCP server. Unblocked calls only the read-only tools you select, at the moment a question needs them:

• searchFinds lines matching a substring or regular expression across every page on a branch, defaulting to the deploy branch.
• readReturns the full MDX of a page, by file path or ID, on a branch or the deploy branch.
• list_nodesWalks the navigation tree of a branch, with optional filters and paginated results.
• read_commentsLists the open comment and suggestion threads on a page, oldest first.
• diffLists all changes between a branch and the deploy branch, with the authors of each change.
• query_analyticsRuns a read-only query on your site’s analytics, covering page views, search, assistant, feedback, and agent and human traffic.

To give Claude Code, Cursor, GitHub Copilot, Codex, or another MCP-compatible AI coding agent access to Mintlify context, connect Mintlify to Unblocked and add the single Unblocked MCP server to your agent.

Unblocked acts as the MCP context layer for your Mintlify data, searching docs pages, comments, and docs analytics alongside your other connected sources and returning cited results through these tools:

• context_researchResearches a question across your connected sources and calls the Mintlify tools you selected when your documentation pages, comments, or analytics are relevant, returning a synthesized answer with citations.
• context_get_urlsFetches the full content behind URLs your agent encounters across connected sources — Jira, Linear, Notion, Confluence, Slack, GitHub, and more.

Questions you (or your agent) can ask Unblocked about your Mintlify data:

• Does our Mintlify page for the webhooks API still match the payload in the latest merged pull request?
• Which docs pages mention the old auth flow, and is there a ticket to update them?
• What are readers searching for in our docs that has no matching page, and has anyone raised it in Slack?
• What open comments are on the quickstart page, and which code changes would resolve them?