FeathersMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-docA | Fetch a full official FeathersJS doc page: returns complete page text plus all code examples. Look up by id, path, or title. Use after get-menu (paths/ids), after search-doc, or when the user gave an exact id/path/title. Prefer id or path over title. |
| get-community-postA | Fetch the full content of a community contribution by id (from search-community results). |
| get-menuA | Get the menu/navigation structure of the FeathersJS documentation. This provides a hierarchical view of the documentation topics and their relationships. Called at the start of each session to understand the organization of the content. |
| get-schemaA | Get the database schema for FeathersJS documentation tables |
| search-docB | Search the FeathersJS documentation for relevant content. You can make multiple calls to this tool to refine your search. Call get-schema and get-menu first to craft better queries. |
| share-knowledgeA | Generate a pre-filled GitHub issue link so the user can submit a community contribution (project, tutorial, or pattern) to the repo. If the user has built or completed something useful with FeathersJS (feature, pattern, tutorial, fix, architecture), proactively ask if they want to share; if they agree, collect title, author, content, tags and call this tool. CRITICAL: your next user-facing reply MUST include the full magic link URL as a clickable Markdown link so the user can open it from chat—do not omit the URL or rely on them reading tool output only. |
| search-communityA | Search real-world FeathersJS solutions from the community. PRIMARY use cases:
You MUST use this when:
After calling:
Returns: results with id for |
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 7 tools
Each tool has a distinct role: get-menu and get-schema provide structural context, search-doc and search-community handle discovery, get-doc and get-community-post retrieve full resources, and share-knowledge handles contribution submission. The doc vs. community split is consistent and clearly reflected in descriptions, so an agent can easily choose the right tool.
All tool names follow the same lowercase hyphenated verb-noun convention: get-doc, get-community-post, get-menu, get-schema, search-doc, search-community, share-knowledge. There are no mixed casing styles or inconsistent verb patterns.
Seven tools is well scoped for a documentation and community knowledge server. The set covers navigation, schema inspection, documentation search/retrieval, community search/retrieval, and contribution sharing without obvious redundancy.
The server covers the main lifecycle: orient with menu/schema, search docs and community, retrieve full items, and share knowledge. Minor gaps exist, such as no explicit listing or filtering of community posts by tag/author, but search largely compensates for those omissions.