Skip to main content
Glama

Server Details

FrontMCP's docs for coding agents: search, pages, APIs, examples and upgrades, by FrontMCP release.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A4.2/5.0

Scored across 9 tools

Disambiguation5/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness4/5

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
Vendor relationship
Not applicable
Privacy policy
Not provided
Trust center
Not applicable
Restrictions
No setup restrictions

Available Tools

9 tools
get_exampleGet a page's exampleA
Read-only
Inspect

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 pageA
Read-only
Inspect

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 skillA
Read-only
Inspect

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 versionsA
Read-only
Inspect

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 pagesA
Read-only
Inspect

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 APIA
Read-only
Inspect

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 projectA
Read-only
Inspect

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 docsA
Read-only
Inspect

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 releasesA
Read-only
Inspect

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

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources