FrontMCP docs
Server Details
FrontMCP's docs for coding agents: search, pages, APIs, examples and upgrades, by FrontMCP release.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 9 tools
Each tool occupies a distinct slot in the retrieval workflow: browse (list_pages), full-text search (search_docs), symbol lookup (lookup_api), read (get_page), runnable code (get_example), skills (get_skill), version selection (get_versions / resolve_version) and diffs (whats_changed). The descriptions explicitly route between near-neighbors, e.g. 'for the docs themselves use search_docs or get_page, and for runnable code get_example' and 'for an API, option or error code by name, lookup_api is more precise'. The only mild overlap is the finder trio, but it is clearly tiered by intent.
Nearly all tools follow a consistent snake_case verb_noun pattern (get_page, list_pages, search_docs, lookup_api, resolve_version, whats_changed). The only deviation is whats_changed, which drops the underscore in 'whats' and reads as a phrase rather than verb_noun.
Nine tools sit squarely in the well-scoped range, and each covers a distinct capability of a documentation server (browse, search, lookup, read, examples, skills, versions, changelog). No tool appears redundant or like padding.
The read-only docs lifecycle is well covered end to end: discover a path, resolve the right version, read the page, pull runnable examples and skills, and diff releases for upgrades. Minor gaps remain, such as no search scoped to examples or skills specifically, and release notes are only reachable indirectly through get_versions or whats_changed.
Publisher details
- Operator
- Frontegg LTD · Publisher source
- Operator website
- https://frontegg.com · Publisher source
- Vendor relationship
- Not applicable
- Documentation
- https://frontmcp.dev · Publisher source
- Privacy policy
- Not provided
- Trust center
- Not applicable
- Restrictions
- No setup restrictions
Available Tools
9 toolsget_exampleGet a page's exampleARead-onlyInspect
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.
Inputs: path (required), index, version.
get_pageRead a docs pageARead-onlyInspect
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.
Inputs: path (required), section, version.
get_skillRead a FrontMCP skillARead-onlyInspect
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.
Inputs: file, name.
get_versionsList the documented versionsARead-onlyInspect
Lists the FrontMCP releases these docs cover, newest first, each with its release notes and the endpoint that pins it (https://mcp.frontmcp.dev/). Says which version this endpoint serves. To find the version a project uses, call resolve_version.
Inputs: no named parameters.
list_pagesList the docs pagesARead-onlyInspect
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.
Inputs: section, version.
lookup_apiLook up an APIARead-onlyInspect
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.
Inputs: symbol (required), limit, version.
resolve_versionFind the docs version for a projectARead-onlyInspect
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.
Inputs: range, lockfile, workspace, packageJson, +1 more.
search_docsSearch the docsARead-onlyInspect
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.
Inputs: query (required), limit, section, version.
whats_changedWhat changed between two releasesARead-onlyInspect
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.
Inputs: from (required), to, limit, section.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
AgentDocs (agentdocs.eu) MCP: read, search, write, comment, share & attach images to Markdown docs.
MCP server for agentverse documentation, generated by doc2mcp.
MCP server for uagents documentation, generated by doc2mcp.
MCP server for the Durable Agent Directory: search and compare agent tools; post to Field Notes.
Related MCP Servers
- FlicenseNot gradedqualityAmaintenanceThis MCP server enables AI clients to search and retrieve current technical documentation for supported agent frameworks over stdio or SSE.-
- AlicenseAqualityDmaintenanceProvides access to Agno framework documentation for AI agents, enabling search and retrieval of SDK references, API endpoints, code examples, and integration guides through MCP-compatible tools.73MIT
- FlicenseNot gradedqualityBmaintenancePublic MCP front door for Spala agent discovery, providing onboarding, documentation search, and template/addon listings for planning backend workflows.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search a daily-refreshed index of official documentation and read whole sections of it, so answers come from current pages with citations. Covers Claude Code, Cursor, Codex and MCP through two tools over MCP or REST.2MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.