Fider MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIDER_URL | No | Your Fider instance URL (e.g., https://feedback.example.com) | |
| FIDER_API_KEY | No | Optional API key for authentication (required for creating, editing, and deleting posts) | |
| FIDER_BASE_URL | No | Your Fider instance URL (e.g., https://feedback.example.com) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_postsC | List posts from Fider with optional filtering |
| get_postA | Get a specific post by its number |
| create_postA | Create a new post (requires authentication) |
| edit_postA | Edit an existing post (requires collaborator/admin role) |
| delete_postB | Delete a post (requires admin role) |
| respond_to_postA | Respond to a post by changing its status (requires collaborator/admin role) |
| list_commentsA | List comments for a specific post |
| add_commentB | Add a comment to a post (requires authentication) |
| update_commentA | Update a comment (requires authentication and ownership) |
| delete_commentA | Delete a comment (requires authentication and ownership/admin) |
| list_tagsA | List all available tags |
| create_tagA | Create a new tag (requires admin role) |
| update_tagB | Update an existing tag (requires admin role) |
| delete_tagA | Delete a tag (requires admin role) |
| assign_tagA | Assign a tag to a post (requires collaborator/admin role) |
| unassign_tagA | Unassign a tag from a post (requires collaborator/admin role) |
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 16 tools
Each tool targets a distinct resource-action combination (posts, comments, tags, responses) with clear boundaries. No two tools appear to perform the same operation on the same resource.
Most tools follow a verb_noun pattern (e.g., list_posts, create_post, delete_comment). Minor inconsistency exists between 'add_comment' and 'create_post'/'create_tag', and 'respond_to_post' uses a multi-word verb, but the overall pattern is predictable.
At 16 tools, the set is slightly above the typical 3-15 range but still well-scoped for managing posts, comments, tags, and statuses. Each tool is necessary, and the count is not excessive.
The tool surface provides full CRUD for posts, comments, and tags, plus assignment and status-change operations. No obvious gaps exist for the domain of a feedback management server; list_posts offers filtering, and response handling is covered.