# Docs for Your Agent

> Give your coding agent FrontMCP's docs for the release your project uses, through FrontMCP's own MCP server at frontmcp.dev/mcp.

Source: https://frontmcp.dev/learn/docs-for-your-agent

A coding agent knows FrontMCP from whatever release it was trained on, if any. FrontMCP's docs server gives it these docs instead, over MCP, for the release your project uses: it searches them, reads pages and sections, looks up an API by name, returns runnable examples, and says what changed between two releases.

**You will learn**
- How to connect your agent to the docs server
- How to pin it to the FrontMCP release your project uses
- What each of its tools does

## Connecting your agent

The server is at `https://frontmcp.dev/mcp`. It needs no key and no sign-in, and it only reads. With Claude Code:

```bash
claude mcp add --transport http frontmcp-docs https://frontmcp.dev/mcp
```

Clients that keep their servers in a JSON file take an entry with the URL:

```json
{ "mcpServers": { "frontmcp-docs": { "url": "https://frontmcp.dev/mcp" } } }
```

The field that marks an entry as a URL differs between clients (`type`, `transport`, or none), so check your client's documentation for it. The server speaks MCP from 2024-11-05 to 2026-07-28 over Streamable HTTP, as any FrontMCP server does.

## Pinning a release

`https://frontmcp.dev/mcp` serves the docs of the latest release. To pin one, add it to the URL:

| URL | Docs for |
| --- | --- |
| `https://frontmcp.dev/mcp` | The latest release |
| `https://frontmcp.dev/mcp/1.9.4` | That release |
| `https://frontmcp.dev/mcp/1.9` | The newest patch of 1.9 |

The server documents each release from 1.9.2 on, and `get_versions` lists them; the [versions page](https://frontmcp.dev/versions) has every release's notes. Without a pin, your agent can find the release itself: the server tells it to call `resolve_version` with your project's `package.json` or lockfile first, and to pass the release it gets to the other tools.

## What it offers

| Tool | What it does |
| --- | --- |
| `resolve_version` | Which documented release a project should read, from its lockfile (npm, Yarn or pnpm), its `package.json` or a version range, and the URL that pins it |
| `get_versions` | The documented releases, newest first, with their release notes |
| `search_docs` | Full-text search over the docs, by section: the page, the heading, the path with its `#anchor`, and the start of its text |
| `get_page` | A page as Markdown, or one section of it. It takes a path, a frontmcp.dev URL, or a link to the old docs on docs.agentfront.dev, which it maps to its page here |
| `list_pages` | The docs as the sidebar has them: Learn, Reference, Examples and Compare |
| `lookup_api` | An API by name: a decorator (`@Tool`), a function (`createFetchHandler`), an option, an error code (`TOOL_NOT_FOUND`) or a CLI flag, with what the Reference says and where |
| `get_example` | A page's Playgrounds, or one's files and tests, with how to run them in your project |
| `whats_changed` | Between two releases: their release notes, every "Changed in" note in the docs with its page, and the pages that changed |
| `get_skill` | FrontMCP's skills catalog: instructions for building with FrontMCP, and their reference files |

It also has one prompt, `upgrade_frontmcp`, which asks your agent to move a project from one release to another, change by change.

**Deep dive: How the server is built**
It's a FrontMCP server on a Cloudflare Worker: [`createFetchHandler()`](https://frontmcp.dev/reference/sdk/create-fetch-handler) behind a Worker entry, as [Cloudflare Workers](https://frontmcp.dev/reference/deployment/cloudflare-workers) describes. Each release's docs come from this site's history: when a release moves the site to the next one, the outgoing release's pages are kept, and the server reads them as Markdown, with a search index and an index of the Reference's APIs, from the Worker's static assets.

## Troubleshooting

### `Too many requests: at most 120 a minute from one address.`

The server answers each address 120 requests a minute, then `429` with `Retry-After: 60`. Wait a minute, or have your agent search before it reads pages one by one.

### `FrontMCP 1.8.7 isn't documented here.`

The server documents releases from 1.9.2 on. Pin the nearest one, or ask `whats_changed` with `from` set to your release to see what changed since, which also covers releases the server doesn't document.