FrontMCP docs

Returns a runnable example from a FrontMCP docs page: the files of one of its Playgrounds, with their tests, as the docs run them. Without `index`, lists the page's Playgrounds (numbered from 1, in page order) with their section and files.

Returns a FrontMCP docs page as Markdown, or one section of it. `path` is a path (/reference/sdk/tool), a frontmcp.dev URL, or an old docs.agentfront.dev URL, which is mapped to its page here; a #anchor in it, or `section`, picks the section. A very long page comes back as its introduction and its sections, to read one at a time. Use it once search_docs, lookup_api or list_pages has given a path, or for a docs URL you already have. The page is the one documented for `version`.

FrontMCP's skills catalog (@frontmcp/skills): instructions for building with FrontMCP, from setting up a project to production readiness. Without `name`, lists the skills. With `name`, returns its SKILL.md and the reference files beside it; with `file` too, that file. Skills are step-by-step guides written for coding agents: for the docs themselves use search_docs or get_page, and for runnable code get_example. The catalog is the newest FrontMCP release's, so the tool takes no version.

Lists the FrontMCP releases these docs cover, newest first, each with its release notes and the endpoint that pins it (https://mcp.frontmcp.dev/<version>). Says which version this endpoint serves. To find the version a project uses, call resolve_version.

Takes no parameters.

Lists the FrontMCP docs as the site's sidebar has them, in reading order: Learn (lessons), Reference (APIs, options, deployment), Examples and Compare, each in groups of pages with their titles and paths. Use it to browse, or to find a page by topic when you don't know its name; to find something specific, search_docs or lookup_api is faster. Read a page it lists with get_page. The pages are those of `version`.

Finds a FrontMCP API by name in the Reference pages: a decorator (`@Tool`), function or method (`createFetchHandler`, `this.elicit`), option (`inputSchema`, `throttle`), error code (`TOOL_NOT_FOUND`), CLI command or flag (`--target`). Returns the matching entries, most relevant first, each with what the docs say, its page and anchor. Read more with get_page.

Says which documented FrontMCP version a project should read, and the endpoint that pins it. Pass the project's package.json, its lockfile (package-lock.json, yarn.lock or pnpm-lock.yaml, including relevant importers and all SDK resolutions), or a version range. An unambiguous lockfile identifies an installation; package.json only the range it allows. If several installations exist, select an npm/pnpm workspace or pass an exact installedVersion read from the resolved SDK package. Call it first when you can read the project.

Full-text search over the FrontMCP docs, by section: page titles, section headings and prose. Returns up to `limit` sections, best first, each with its page, heading, path (with the #anchor) and the start of its text. Read one with get_page. For an API, option or error code by name, lookup_api is more precise.

What changed in FrontMCP after `from` up to `to` (the endpoint's version by default): each release's notes, every note the docs make about a change ("Changed in 1.9.5: before, …"), with its page and section, and, when both versions are documented, which pages changed. `from` can be any release, documented or not. Use it to upgrade a project, or to check whether docs for one version hold for another.