> ## Documentation Index > Fetch the complete documentation index at: https://docs.getmillwork.dev/llms.txt > Use this file to discover all available pages before exploring further. # Documentation MCP > Connect a coding assistant to a read-only search over these docs that needs no API key and cannot touch your organization. The **documentation MCP** is a live, read-only search over this documentation that a coding assistant such as Claude, Codex, Cursor, or Gemini can connect to. It is for anyone who wants an assistant to answer Millwork questions from the current docs instead of from memory. It is a different thing from the [execution MCP](/mcp/execution), `@millwork/solver-mcp`, which lets an assistant use the Millwork API with your organization API key. The documentation MCP needs no API key and answers only from these pages. It grants no authority to run, change, or read anything in your organization. ## What the two tools do `search_millwork` takes a plain-language question or phrase and returns excerpts from the pages that match, each with its title and a link to the page. Use it for questions such as "when is the platform fee charged" or "how do I retry a run". `query_docs_filesystem_millwork` takes a read-only command against a private copy of the documentation, where every page is a `.mdx` file, and returns the command's output: a page's Markdown, matching lines, or a directory listing, up to 30 KB per call. Reading `/concepts/access.mdx` returns that page in full. The copy holds only these docs and their OpenAPI file; the command runs nowhere else and touches no other file or network. Both tools answer only from this documentation. Neither one can call the Millwork API. ## Connect it to your assistant The documentation MCP is hosted for Millwork by the documentation platform; you do not install or run anything. Its server card on the documentation site names the endpoint and the two tools: ```text theme={null} https://docs.getmillwork.dev/.well-known/mcp/server-card.json ``` Open the card, copy the value of its `url` field, and add that address as a remote MCP server in your assistant's MCP settings. Leave every key and token field empty: the server accepts no authentication and asks for none. A configuration needs only that URL: ```json theme={null} { "mcpServers": { "millwork-docs": { "url": "" } } } ``` You do not need an MCP connection to work with an assistant. **Copy page** at the top of any page copies it as Markdown, **View as Markdown** gives a URL to share, `/llms.txt` lists every public page with its one-line description, and `/llms-full.txt` holds the complete documentation in one file. [Use a coding assistant](/get-started/use-with-an-assistant) explains that workflow and the rules to give the assistant. ## What it cannot do The documentation MCP grants no authority to run, change, or read anything in your organization. It cannot see your runs, your API keys, your provider connections, your members, or your balance, and it cannot start, cancel, or change anything. An assistant that reaches these docs through it has read the docs and nothing more. A question about your own account, such as why a run failed or what your balance is, needs the dashboard or the API with your organization API key. The assistant can read the page that explains the answer; sending the request is still yours to do. Give an assistant one page and the rules that keep every change with you. Let an assistant use the Millwork API with your organization API key.