Formidable MCP Companion
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| --docs | Yes | Path to the local documentation corpus directory containing the mirrored markdown and metadata. | |
| --update-docs | No | Optional flag to refresh the documentation corpus before the server starts. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_docsA | Search Formidable Forms documentation. Returns ranked sections with a snippet, heading, anchor, and doc id. Pass the doc id + anchor to read_doc_section for the full section. |
| read_doc_sectionA | Read one section of a documentation article by anchor or heading. Prefer this over read_doc; a section is typically a few hundred tokens. |
| read_docA | Read a complete documentation article. Large articles can exceed 30,000 tokens; use search_docs + read_doc_section when possible. |
| list_docsB | List documentation articles, optionally filtered by category path. |
| get_doc_structureB | Show the heading/anchor table of contents for one article. |
| browse_docs_by_categoryA | Browse a category: returns its subcategory paths and every article inside it, including nested subcategories. |
| list_categoriesA | List every documentation category path with article counts. |
| get_docs_infoA | Report corpus metadata: article count, categories, last sync, and how many days old the local copy is. |
| update_docsA | Refresh the documentation corpus from formidableforms.com. Fetches only articles whose upstream last-modified timestamp changed unless force=true. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Most tools target distinct documentation operations, and the descriptions clearly steer agents from search to section reading. There is mild overlap between list_docs, browse_docs_by_category, and list_categories, but the descriptions make their boundaries understandable.
All tools use snake_case and generally follow a predictable verb_noun pattern such as search_docs, read_doc_section, list_categories, and update_docs. The minor variation in browse_docs_by_category is readable and still consistent with the overall convention.
Nine tools is well-scoped for a documentation companion server. Each tool supports a distinct part of the discover, browse, read, and refresh workflow without excessive surface area.
The tool set covers the full documentation lifecycle: discovery via search and listing, navigation via categories and structure, reading at section and article levels, metadata inspection, and corpus refresh. No obvious retrieval or maintenance gaps remain.