Admin Model Context Protocol (MCP) server

About the admin MCP

The admin MCP server gives AI tools write access to your Docfiy content and settings. Use it to update content and access your dashboard. With the admin MCP, you can use your preferred AI tools to edit pages, restructure navigation, update docs.json, open pull requests, change settings, create workflows, and more.

Connect any MCP client like Claude, Claude Code, or Cursor to the admin MCP server to collaborate on your Docfiy content and settings with the same tools you use to write code. When you use the admin MCP server, all changes happen on a branch and require a pull request to merge.

How the admin MCP differs from the search MCP

Connect to the admin MCP

You must have an interactive OAuth login against your Docfiy account to connect to the admin MCP. AI tools exchange that login for a session token scoped to one project.

claude mcp add --transport http docfiy https://mcp.docfiy.com

{
  "mcpServers": {
    "docfiy": {
      "url": "https://mcp.docfiy.com"
    }
  }
}

How a session works

Every admin MCP session binds to a single Git branch. The flow is:

What the admin MCP can do

Content

• read — Fetch the full MDX of any page on the session branch.
• search — Find lines matching a substring or regular expression across every page.
• edit_page — Apply a targeted edit to a page.
• write_page — Overwrite a page's full MDX content.

Navigation

• list_nodes — Walk the navigation tree with optional filters. Filter by parentId (use recursive: true to include all descendants), one or more node types, or any division scope: language, version, tab, dropdown, anchor, product, or item. Results are paginated through an opaque cursor.
• create_node — Add a new page, group, tab, anchor, version, language, product, or dropdown.
• update_node — Update a node's properties in place (rename a group, change an icon, set a default version).
• move_node — Move a node, including renaming a page's path.
• delete_node — Remove a node from the navigation.

Configuration

• update_config — Modify docs.json (theme, navigation roots, integrations, SEO settings).

Session

• checkout — Bind the session to a branch.
• list_branches — List Git branches available for the project, with optional query filtering. Returns the branch names, total count, and the deploy branch. Call this before checkout to attach to an existing branch by name.
• get_session_state — Inspect the current branch, edited files, and pending nav diff.
• diff — List all changes between the session and main.
• save — Open a pull request or commit to the session branch.
• discard_session — Drop the session and its in-flight changes.

Example prompts

After you connect the admin MCP, you can drive it with natural-language prompts. For example:

• "Check out a branch called add-billing-faq and create a new page under the FAQ group titled 'Billing'. Draft answers for the five questions in this Linear issue."
• "Find every page that mentions the deprecated legacy_token field and update the example to use api_key instead. Save as a PR titled 'docs: replace legacy_token references'."
• "Reorganize the API reference: move the webhooks pages into a new group called 'Webhooks' and update the icons to match the rest of the section."

Best practices