# Minlify Admin MCP MCP Server > **Minlify Admin MCP MCP Server** is a hosted, multitenant Model Context Protocol (MCP) server run by **MewCP** (https://mewcp.com), giving AI agents managed access to Minlify Admin MCP. > > MewCP takes care of all MCP infrastructure for you — credential storage, OAuth flows, > token refresh, and production-grade auto-scaling — so your AI agents can connect to > third-party services and run freely without you managing any MCP server yourself. > > Server page: https://mewcp.com/mcp/mintlify-admin-mcp > MewCP docs: https://docs.mewcp.com > Full catalog: https://mewcp.com/llms.txt --- ## About Mintlify Admin MCP lets AI agents create and edit documentation, restructure navigation, modify site configuration and SEO settings, manage branches, and open pull requests directly in Mintlify. --- ## Details - Server ID: `mintlify-admin-mcp` - Version: 1.0.0 - Tools: 33 - Authentication: OAuth, managed by MewCP - Transport: http --- ## Access The gateway URL below serves your **entire MewCP toolset**, not this server on its own. Pasting a config snippet is not enough — Minlify Admin MCP has to be in the toolset first. In order: 1. Add Minlify Admin MCP to your toolset at https://mewcp.com/mcp/mintlify-admin-mcp 2. Connect your Minlify Admin MCP account (OAuth); MewCP stores the credential and attaches it to each call 3. Copy your MewCP API key from the dashboard (Developer) 4. Configure your client with the snippet for it below Once connected, an agent does **not** see this server's tools as top-level tools. It sees four meta-tools and reaches everything through them: - `search(query)` — find tools by keyword across the toolset - `get_schema(tools)` — full description and arguments for the tools you picked - `list_accounts(provider)` — only when one app has several connected accounts - `call_tool(server_maskedId, tool_name, args)` — execute So the list below is what `search` can return for this server, not a set of callable tool names on their own. --- ## Tools (33) Descriptions are truncated to 160 characters; call `get_schema` for the full text and the argument schema. Where a tool is annotated, its type is shown — treat `destructive` as irreversible. - `read` _(read)_ — Read the full MDX content of a single page on the current branch. Reflects in-session edits made via edit_page/write_page, not just the published version.… - `search` _(read)_ — Find lines matching a substring or regex across every page on the current branch. Returns { matches, truncated } where each match is { path, lineNumber, line… - `list_nodes` _(read)_ — List navigation nodes with optional filters over the current branch nav tree. `parentId: null` returns root-level nodes; a string returns direct children of… - `get_session_state` _(read)_ — Get current session state including branch name, edited files, and nav diff - `diff` _(read)_ — Returns the list of changes between current session and main. Each entry lists `authors`, the members whose unpublished edits it contains, and `byYou`, whether… - `edit_page` _(write)_ — String-replace edit on a page Y.Doc body. `path` is the page href or markdown file path (e.g. "/quickstart" or "guides/setup.mdx"), with or without a leading… - `write_page` _(write)_ — Full overwrite of a page Y.Doc content. `path` accepts the same forms as `read` and `edit_page`: the page href or markdown file path, with or without a leading… - `create_node` _(write)_ — Insert a node into the navigation tree under `parentId` (null = root). `order` is clamped into siblings and defaults to append. `data` is discriminated by… - `update_node` _(write)_ — Update a navigation node's properties in place by nodeId — no repositioning. `data` is a discriminated union on `type` carrying partial, type-specific fields… - `delete_node` _(destructive)_ — Remove a node and its subtree from the navigation tree by `nodeId`. For pages in the removed set, the hocuspocus room, document S3 blob, and baseline (Redis +… - `move_node` _(write)_ — Reposition a node in the navigation tree by nodeId. `parentId: null` moves to root; omit to keep the current parent. `order` is 0-based among the new siblings;… - `upload_image` _(write)_ — Add a local image file to the docs on the current session branch. Pass `contentType` and the exact `size` in bytes: the result is `{ uploadId, uploadUrl,… - `finalize_image_upload` _(destructive)_ — Save an image you uploaded to the `uploadUrl` from `upload_image` into the docs. Pass the `uploadId` and the destination `path` (and `purpose: 'logo'` for an… - `update_config` _(write)_ — Update any top-level `docs.json` field except `navigation` (use the navigation tree tools for that). This is the ONLY way to change the site-level… - `list_branches` _(read)_ — List all git branches available for a deployment before or after checkout. Pass `subdomain` to target a deployment; it defaults to the active session and is… - `checkout` _(write)_ — Select a deployment and open its editor session in one call. This is an org-wide connection, so `subdomain` is required to choose which deployment to open.… - `save` _(destructive)_ — Flush branch to git. With mode="auto" (default) opens a PR if none exists, otherwise commits to the existing PR branch; it only auto-merges when this… - `discard_session` _(destructive)_ — End the session without creating a PR. On a session branch, deletes the branch if nothing was saved. On the deploy branch, reverts only your own unpublished… - `get_analytics_schema` _(read)_ — Get the ClickHouse schema, event taxonomy, traffic classification rules, and SQL conventions for query_analytics. Call this once before writing analytics SQL.… - `query_analytics` _(read)_ — Run one read-only ClickHouse SELECT against the deployment's documentation analytics (page views, agent vs human traffic, search, assistant, feedback). Rows… - `list_deployments` _(read)_ — List the deployments this connection is authorized for, returning each `{ subdomain, name }`. On an org-wide connection this is every main (non-preview)… - `get_analytics_report` _(read)_ — Read a prebuilt dashboard analytics report for a deployment: traffic KPIs, page views, popular pages, referrals, agent traffic, user flows, CTA clicks,… - `get_workflows` _(read)_ — Read a deployment’s Workflows (scheduled and event-triggered agents) and their runs. `list` returns every workflow; `get` one by `workflowSchemaId`;… - `list_repos_and_prs` _(read)_ — List what workflows can connect to: `list_repos` pages through repositories connected via the org’s GitHub and GitLab installations, `list_pull_requests` lists… - `get_deployment_settings` _(read)_ — Read a deployment’s dashboard settings in one call: `deployment` (name, base path, custom domains, noindex, AI chat, search, add-ons, privacy, custom scripts,… - `manage_custom_domain` _(destructive)_ — Change a deployment’s custom domains. Applies immediately to the live site. `add` attaches a domain, `create_hostname` provisions its Cloudflare hostname and… - `manage_git_source` _(destructive)_ — Change the git repositories a deployment builds from. Applies immediately. `add` appends a source, `update` replaces the source at `index`, `remove` drops it,… - `update_deployment_settings` _(destructive)_ — Change one dashboard setting on a deployment. Applies immediately to the live site, with no branch or PR. Settings: `noindex`, `base_path`, `name`,… - `manage_members_sharing` _(destructive)_ — Manage organization members and private-page sharing. Member actions apply org-wide: `list_members`, `remove_member`, `update_member_roles` (replaces roles),… - `manage_workflow` _(destructive)_ — Create, change, or run a deployment’s Workflows. Applies immediately. `create` and `create_scheduled` (one-time run at `nextRunAt`) take the workflow… - `manage_access_auth` _(destructive)_ — Change who can read a deployment. Applies immediately to the live site. Deployment auth (`update_auth`, `delete_auth`, `add_password`, `delete_password`,… - `manage_workflow_prs` _(destructive)_ — Merge (`merge`, squash) or close (`close`) a Mintlify-generated pull request by `repo` and `prNumber`. Only when the user explicitly asks. - `agent_review_settings` _(destructive)_ — Change whether agent edits push directly to the deploy branch (`push_to_main`) or open a pull request (`create_pull_request`). Applies immediately. Only when… --- ## Connect Gateway URL: https://gateway.mewcp.com/personal/mcp Every request carries one header: Authorization: Bearer Replace `API_KEY` with your own key from the dashboard (Developer). ## Apps ### Claude Desktop Mac & Windows app - macOS: `~/Library/Application Support/Claude/claude_desktop_config.json` - Windows: `%APPDATA%\Claude\claude_desktop_config.json` ```json { "mcpServers": { "mewcp": { "command": "npx", "args": [ "-y", "mcp-remote@latest", "https://gateway.mewcp.com/personal/mcp", "--header", "Authorization: Bearer API_KEY" ] } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. 1. Open Claude Desktop → Settings → Developer → "Edit Config" 2. Paste the snippet inside the outer { } of the config file (merge with your existing "mcpServers" section if you have one) 3. Save the file and restart Claude Desktop 4. Start a new conversation — your tool will be available ### VS Code Copilot / Cline - Command Palette → "MCP: Open User Configuration" (opens mcp.json). For one project only, use .vscode/mcp.json instead. ```json { "mcp.servers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have a "servers" section in your mcp.json? Just add the server entry inside it. 1. Open VS Code → Command Palette (Cmd+Shift+P / Ctrl+Shift+P) 2. Run "MCP: Open User Configuration" to open your mcp.json 3. Paste the snippet and save 4. Start the server when prompted (or from the MCP servers view) and use it in Copilot Chat ### Cursor AI-first editor - macOS: `~/.cursor/mcp.json` - Windows: `%USERPROFILE%\.cursor\mcp.json` ```json { "mcpServers": { "mewcp": { "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your mcp.json? Just add the server entry inside it. 1. Open Cursor → Settings → Cursor Settings → MCP 2. Click "Add new global MCP server" 3. Paste the snippet and save 4. Restart Cursor ### Codex OpenAI's CLI agent - Add the snippet to your Codex MCP config or your standard MCP config file for the CLI tool you use. ```json { "mcpServers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Codex generally reads a standard MCP server block, so you can add this alongside your other configured servers. 1. Open your Codex MCP config or project-level config file 2. Paste the MewCP server block inside the config JSON/TOML structure your tool expects 3. Save the file and restart Codex 4. Verify the tool is available inside a fresh session ### Claude Code Anthropic's CLI agent - ~/.claude.json (user scope) or .mcp.json in your project root — create it if it doesn't exist. Or skip the file and use the CLI command below. ```json { "mcpServers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. 1. Open ~/.claude.json (or .mcp.json in your project root) in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcpServers" section if you have one) 3. Save the file and start (or restart) Claude Code 4. Or skip the file entirely and run the CLI command below instead ### OpenCode Open-source terminal agent - ~/.config/opencode/opencode.json (global) or opencode.json in your project root — create it if it doesn't exist. ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "mewcp": { "type": "remote", "url": "https://gateway.mewcp.com/personal/mcp", "enabled": true, "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcp" section in your opencode.json? Just add the server entry inside it. 1. Open ~/.config/opencode/opencode.json (or opencode.json in your project root) in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcp" section if you have one) 3. Save the file and start (or restart) OpenCode ### OpenClaw Self-hosted agent gateway - ~/.openclaw/openclaw.json — create it if it doesn't exist. ```json { "mcp": { "servers": { "mewcp": { "transport": "streamable-http", "url": "https://gateway.mewcp.com/personal/mcp", "enabled": true, "headers": { "Authorization": "Bearer API_KEY" } } } } } ``` Already have an "mcp" section in your openclaw.json? Just add the server entry inside "servers". 1. Open ~/.openclaw/openclaw.json in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcp" section if you have one) 3. Save the file and restart OpenClaw ### Antigravity Google's agentic IDE - ~/.gemini/config/mcp_config.json (global) or .agents/mcp_config.json (workspace-local) — create it if it doesn't exist. ```json { "mcpServers": { "mewcp": { "serverUrl": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. Remote servers must use the "serverUrl" field — the legacy "url"/"httpUrl" fields aren't supported. 1. In the editor's agent side panel, click "…" → "MCP Servers" → "Manage MCP Servers" → "View raw config" (Antigravity CLI: type /mcp instead to open the Interactive MCP Manager) 2. Paste the snippet inside the outer { } (merge with your existing "mcpServers" section if you have one) 3. Save the file — the server connects automatically ### Hermes Nous Research's CLI agent - config.yaml in your Hermes config directory (~/.hermes) — add this under a top-level "mcp_servers:" key. ```yaml mcp_servers: mewcp: url: "https://gateway.mewcp.com/personal/mcp" headers: Authorization: "Bearer API_KEY" ``` Already have an "mcp_servers" section in your config.yaml? Just add the server entry inside it. 1. Open config.yaml in your Hermes config directory 2. Paste the snippet under the top-level "mcp_servers:" key (merge with existing entries if you have any) 3. Save the file, then run /reload-mcp in Hermes (or start a fresh session) 4. Ask Hermes "Tell me which MCP-backed tools are available right now" to confirm it connected ### DeepSeek Harness DeepSeek's agent harness - cordis.yml in your DSH project — or the patch file you mount plugins from. ```yaml - id: mcp-mewcp name: '@deepseek-ai/dsh-mcp-client' config: serverName: mewcp transport: streamable-http url: https://gateway.mewcp.com/personal/mcp headers: Authorization: "Bearer API_KEY" ``` One plugin instance = one MCP server. Add this entry to your plugin list; don't nest it inside another entry. 1. Open cordis.yml (or your patch file) in your DSH project 2. Paste the entry into your plugin list, keeping the leading dash and indentation 3. Restart DSH (or let HMR reload) — tools register as mcp__mewcp__ 4. Verify with: dsh web --dump-config | grep -A3 mcp ## SDKs ### Python fastmcp client ```python import asyncio from fastmcp import Client from fastmcp.client.transports import StreamableHttpTransport SERVER_URL = "https://gateway.mewcp.com/personal/mcp" API_KEY = "API_KEY" transport = StreamableHttpTransport( url=SERVER_URL, headers={ "Authorization": f"Bearer {API_KEY}", } ) async def main(): client = Client(transport) async with client: tools = await client.list_tools() print(tools) asyncio.run(main()) ``` 1. Install fastmcp: pip install fastmcp 2. Copy the snippet into your project 3. Replace API_KEY with your key from the dashboard 4. Run your script ### TypeScript MCP SDK ```typescript import { Client } from "@modelcontextprotocol/sdk/client/index.js"; import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js"; const SERVER_URL = "https://gateway.mewcp.com/personal/mcp"; const API_KEY = "API_KEY"; const transport = new StreamableHTTPClientTransport(new URL(SERVER_URL), { requestInit: { headers: { Authorization: `Bearer ${API_KEY}`, }, }, }); const client = new Client({ name: "mewcp-client", version: "1.0.0" }); await client.connect(transport); const tools = await client.listTools(); console.log(tools.tools.map((t) => t.name)); ``` 1. Install: npm install @modelcontextprotocol/sdk 2. Copy the snippet into your project 3. Replace API_KEY with your key from the dashboard 4. Run with Node 18+ as an ES module (e.g. npx tsx script.ts)