Mintlify MCP

Live

OAUTH 2.0

DEVELOPER TOOLS

Developer Tools

Connect to Mintlify MCP. Read and edit documentation pages, manage navigation nodes, search content, and publish changes via pull requests from your AI...

  • Acts as the user: Every tool call runs as the authorizing user. Access and audit trail stay intact.
  • Credentials stay vaulted: AES-256 encrypted, resolved at request time, never stored in LLM context.
  • Scoped before every call: Per-user permissions enforced automatically. 90-day audit trail included.
Mintlify MCP
agent · Acme Q3
Run
Checkout in Mintlify MCP
S
mintlifymcp_checkout
85ms
Mintlify MCP agent
Bind the current session to a git branch, creating it if it does not exist. returns the branch name, editor url, and a t.
Sources: Mintlify MCP
mintlifymcpmcp
1 tool call
18:29
Message Claude...

Tools your agent reaches for on Mintlify docs, scoped per user.

CALL ANY TOOL
Read, edit, and publish documentation through branches and pull requests, as the authoring user.
mintlifymcp_checkout
Bind the current session to a git branch, creating it if it
Bind the current session to a git branch, creating it if it does not exist. returns the branch name, editor url, and a toolkit list of recommended tools to use next.
Parameters
Name
Type
Required
Description
branch
string
Optional
Specific branch to bind to. If it exists in git the session attaches to it without creating a branch; if not, it is created from `from`. Cannot be the deploy branch. Omit to auto-generate a fresh `admin-mcp/-<7-char-sha>` branch.
from
string
Optional
Base branch to fork from when creating a new branch. Defaults to the deployment's configured deploy branch (typically `main`). The new branch is created at this branch's latest commit.
slug
string
Optional
Human-readable slug used to name an auto-generated branch as `admin-mcp/-<7-char-base-sha>`. Ignored when `branch` is provided. If omitted and `branch` is also omitted, the branch is auto-named `admin-mcp/` and is not human-recognizable. Use a stable, kebab-case slug (e.g. `add-tips-page`).
mintlifymcp_create_node
Insert a new node (page, group, tab, anchor, version, langua
mintlifymcp_delete_node
Remove a node and all its descendants from the navigation tr
mintlifymcp_diff
Return the list of changes between the current session branc
mintlifymcp_discard_session
End the current editing session without creating a pull requ
mintlifymcp_edit_page
Apply a string-replace edit to a page's mdx body content. us
mintlifymcp_execute
Run typescript or javascript against the admin mcp dashboard
mintlifymcp_get_session_state
Return the current session state including the active branch
mintlifymcp_list_branches
List all git branches available for the current deployment,
mintlifymcp_list_nodes
List navigation nodes from the current branch tree with opti
mintlifymcp_move_node
Reposition a navigation node by moving it to a new parent or
mintlifymcp_read
Read the full mdx content of a single page on the current br
Build your Agent
Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.
Python · LlamaIndex
from langchain_mcp_adapters.client import MultiServerMCPClient
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="mintlifymcp")

mcp = MultiServerMCPClient({
"mintlifymcp": {
"url": "https://mcp.scalekit.com/mintlifymcp",
"headers": {"Authorization": "Bearer " + token}
}
})
tools = await mcp.get_tools()
import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "mintlifymcp" });

const openai = new OpenAI();
// Connect to MCP at https://mcp.scalekit.com/mintlifymcp
// Pass: Authorization: Bearer + token
import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "mintlifymcp" });

const anthropic = new Anthropic();
// Connect to MCP at https://mcp.scalekit.com/mintlifymcp
// Pass: Authorization: Bearer + token
from google.adk.agents import LlmAgent
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="mintlifymcp")
# Connect to MCP at https://mcp.scalekit.com/mintlifymcp
# Pass: Authorization: Bearer + token
Try these prompts
Copy any prompt into your agent. Each maps directly to a Mintlify tool. Click to copy, paste into your agent, done.
Get started
Copy the prompt
Copied
Fully overwrite a page’s MDX content on the current branch by path?
Copy the prompt
Copied
Update a navigation node’s properties in place by node ID, including page frontmatter fields like title, description, ic?
Advanced
Copy the prompt
Copied
Search the Admin MCP SDK for available methods by keyword to find the right operation before writing an execute script?
Copy the prompt
Copied
Flush branch changes to git by opening a pull request or committing directly, depending on the selected mode?
SEE HOW AUTH WORKS
Your users connect once. Their Mintlify credentials stay vaulted, every call is scope-checked, and every action is logged.
1
Authorize
Your user connects
Mintlify MCP
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Mintlify MCP
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Mintlify MCP
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Mintlify MCP
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
See the same per-user auth pattern across other connectors.
ENGINEERING
DevOps assistant agent
Triage GitHub incidents, open Linear tickets, and notify the on-call channel in Slack with context already attached.
ENGINEERING
Auto-release notes agent
Group merged GitHub PRs by feature, fix, or chore and publish release notes per tag. No manual changelog grooming.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Other connector libraries treat auth as a demo afterthought. Scalekit starts with identity, scope enforcement, and audit. Connectors follow.
01.
Shared tokens break per-user analytics
A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential.
// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
One connector today. Ten tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions

Does the agent access Mintlify as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Mintlify OAuth token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Mintlify?
Yes. Pass a tool name filter to listScopedTools so the DevOps agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Mintlify.

What happens when a user revokes Mintlify access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Do docs edits go straight to production?
No. Page edits and navigation changes go through Mintlify's branch and pull request flow, attributed to the authorizing user. Nothing publishes without the review step your repo enforces.

Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""mintlifymcp"": {
""url"": ""https://mcp.scalekit.com/mintlifymcp"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.mintlifymcp]
url = ""https://mcp.scalekit.com/mintlifymcp""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""mintlifymcp"": {
""url"": ""https://mcp.scalekit.com/mintlifymcp"",
""type"": ""http""
}
}
}