> ## Documentation Index
> Fetch the complete documentation index at: https://ctrlrun.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Use the docs from your editor

> This documentation is an MCP server. One configuration block adds it to Cursor, VS Code or any MCP client, so the assistant answers from these pages.

This documentation is an MCP server, hosted with the site by Mintlify at the site's `/mcp`
path, exposing one tool: a search across every page here. Add it to your coding tool and the
assistant answers from the current pages rather than from whatever it remembers.

## The configuration

For Cursor, in `mcp.json`:

```json theme={null}
{
  "mcpServers": {
    "ctrlrun-docs": { "url": "https://ctrlrun.dev/mcp" }
  }
}
```

For VS Code and other clients that take a `servers` block:

```json theme={null}
{
  "servers": {
    "ctrlrun-docs": { "type": "http", "url": "https://ctrlrun.dev/mcp" }
  }
}
```

Both shapes are the ones Mintlify's documentation gives for a hosted docs server (read
2026-09-06). The path is always `/mcp` on whatever host serves this site.

## Three questions it can now answer

* *What happens in CTRLRun when a tool call times out?* The assistant finds
  [Outcomes and AMBIGUOUS](/concepts/outcomes-and-ambiguous) and answers that a timeout is
  `AMBIGUOUS`, not `FAILED`, and that a retry is refused until a human or a reconcile hook
  resolves it.
* *How do I put an approval in front of one MCP tool but not another?* It finds the
  [policy reference](/reference/policy-yaml) and the
  [gateway page](/mcp/gateway-in-5-minutes): one entry per tool, `approve` on one, `allow` on
  the other.
* *Does the receipt chain prove who wrote a receipt?* It finds
  [Receipts and evidence](/concepts/receipts-and-evidence) and answers no: the chain detects
  alteration and is not a signature.

## What it is not

It is not enforcement. An assistant that can search this documentation can tell you what the
gateway does; it cannot stand in the agent's path. An agent that called a CTRLRun tool to check
its own actions could also choose not to, which is why the gateway is a process between the
agent and its tools and not a tool the agent picks.

## Next

* [CTRLRun and MCP](/mcp/overview).
* [Get started](/get-started/quickstart) · [Why](/why).


## Related topics

- [CTRLRun and MCP](/mcp/overview.md)
- [Use the LangGraph adapter](/guides/langgraph-adapter.md)
- [An IAM agent that can grant read but never admin](/cookbook/iam-agent.md)
- [Approve from your assistant](/mcp/approve-from-your-assistant.md)
- [CTRLRun and agent oversight toolkits](/compare/governance-toolkits.md)