# Docs for AI agents

Give your coding assistant access to the same guides and generated API reference you read
here. The documentation server only reads public documentation; it cannot call the Fin API,
access accounts, approve actions or move funds.

## Connect over MCP

The docs server exposes a Streamable HTTP MCP endpoint at `/mcp`:

```text
https://docs.fin.benkurrek.com/mcp
```

Add that URL as a remote HTTP MCP server in your assistant's connection settings. Public
documentation does not require your Fin partner key or an end-user token.

The endpoint is available when the docs version containing this feature is deployed. For a
local preview, replace the origin with the preview site's address and keep `/mcp`; a separate
assistant can connect only if it can reach that address.

## Search, then read

| Tool | Input | Use |
| --- | --- | --- |
| `search_docs` | `{ "query": "approval continuation" }` | Find matching pages. |
| `get_doc` | `{ "id": "<id from search_docs>" }` | Read a matching page's full Markdown. |

Search for a task or resource, then pass a returned page id to `get_doc`. Use endpoint schemas
for request and response fields, and guides for workflows across calls.

The server reads the documentation packaged with that deployment. A local preview can contain
changes that have not yet reached the public site.

For example, ask your assistant:

> Use the Fin documentation MCP to explain how to start a run and reconnect to its event
> stream. Read the authentication and streaming guides, then check the endpoint schemas
> before writing the integration.

## Copy or fetch Markdown

Use **Copy page** to copy a page's Markdown. Its `.md` URL exposes the same content without
navigation or styling, for example:

```text
https://docs.fin.benkurrek.com/quickstart.md
https://docs.fin.benkurrek.com/api-reference/agent-runs/runs-start.md
```

[llms.txt](/llms.txt) provides a compact page index.
[llms-full.txt](/llms-full.txt) provides the documentation as one text file.
Use [OpenAPI](/openapi.json) for the machine-readable API schema.

## Keep credentials in your application

Documentation access requires no API credentials. When moving to real requests, keep your
partner key and user token in your trusted application environment. Follow
[Authentication](/authentication) and [Your first run](/quickstart) for the separate steps
needed to call Fin.