Skip to main content

Willow Docs MCP Server

The Willow documentation is available as a remote MCP server, so your AI tool can look things up while it works instead of you pasting pages into the chat. Ask "how do I set up SCIM with Okta?" or "which scope does the Create Guard endpoint need?", and the agent searches these docs, reads the relevant pages, and answers with links to them.

https://docs.withwillow.ai/mcp

The server is public and read-only. It needs no account or API key, and it serves the same content as this site: every docs deploy updates it.

Tools​

ToolWhat it does
search_docsSearches the docs and returns the best-matching pages with their URL and a short snippet. Optional section and limit arguments.
get_docReturns the full Markdown of a page. Accepts a URL from search_docs or list_docs, or a site path such as /docs/admin/sso-and-auth.
list_docsLists pages with a one-line description of each, for browsing when a search comes back empty. Narrow it with section or path_prefix.

Agents typically call search_docs, then get_doc on the top results. The server tells the agent to work this way when it connects, so you don't need to prompt for it.

Scopes​

By default the server covers all of the documentation. Add a scopes query parameter to limit it to the sections you care about:

ScopeCovers
adminAdmin guides: configuring the gateway, SSO, security, guards, integrations, and deployment. Everything under /docs.
userUser guides: connecting AI tools, skills, toolkits, and the CLI. Everything under /user.
apiThe Willow Admin API reference. Everything under /api.

Combine scopes with commas:

https://docs.withwillow.ai/mcp?scopes=admin,api

A scoped server only searches and lists pages in its scopes, and get_doc refuses pages outside them. With a single scope, the section argument is dropped from the tools, since there is nothing left to choose between. An unknown scope name fails the connection with an error that lists the valid ones.

Scoping is useful when the audience is narrow. An assistant for end users doesn't need the Admin API reference in its results, and an automation that calls the Admin API doesn't need the user guides.

Connect your AI tool​

Use the URL above, with ?scopes= if you want it. The server uses the Streamable HTTP transport.

Cursor: add it to ~/.cursor/mcp.json, or .cursor/mcp.json in a project:

{
  "mcpServers": {
    "willow-docs": {
      "url": "https://docs.withwillow.ai/mcp"
    }
  }
}

Claude Code:

claude mcp add --transport http willow-docs https://docs.withwillow.ai/mcp

Quote the URL if it has a query string, for example "https://docs.withwillow.ai/mcp?scopes=admin,api", so your shell doesn't interpret the ?.

VS Code: add it to .vscode/mcp.json:

{
  "servers": {
    "willow-docs": {
      "type": "http",
      "url": "https://docs.withwillow.ai/mcp"
    }
  }
}

Claude (desktop and web): go to Settings > Connectors > Add custom connector and paste the URL.

Other MCP clients work the same way: add a remote (HTTP) server with the URL and no authentication.

Add it to your Willow gateway​

To give everyone in your organization the docs without each person configuring their own client, add the server to your gateway from the catalog. It then reaches users through their existing Willow connection, with the same groups, toolkits, and logs as your other servers. See Willow Docs connector.

On this page