FrontMCP docs
dev.frontmcp.mcp/frontmcp · v1.0.0
FrontMCP's docs for coding agents: search, pages, APIs, examples and upgrades, by FrontMCP release.
MCPremoteno credentialsFiles & storageKnowledge & docsE-commerce
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 9 tools, protocol 2025-06-18 · checked 2026-10-17
Test & rating
A 100/100
What it does: 9 tools · 9 read, 0 write · Files & storage, E-commerce, Knowledge & docs
Test call list_pages: worked (1,624 ms)
How the rating is made
- Answers without login: +30
- Speed of first answer: +10
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +10
- Read/write annotations: +5
- Safe test call: +20
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://mcp.frontmcp.dev/Tools
9 tools listed at last check
get_exampleReturns 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.get_pageReturns 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 sget_skillFrontMCP'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.get_versionsLists 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.list_pagesLists 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.lookup_apiFinds 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 whatresolve_versionSays 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; the part about @frontmcp/sdk is enough), or a version range. A lockfile gives the installed version; package.jsosearch_docsFull-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 mowhats_changedWhat 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, docu
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/dev.frontmcp.mcp/frontmcp)