add_comment
Add a comment to a post (requires authentication)
LABSCO SUMMARY
Every tool names the role it needs, which is the difference between an agent that fails cleanly and one that fails halfway through.
A feedback board has three permission levels and this surface labels each tool with the one it requires — anonymous for reads, authenticated for posting and commenting, collaborator for tagging and status changes, admin for deletion. That makes the boundary knowable before a call rather than after the request is refused, which matters when an agent is working through a queue of posts and would otherwise stop midway with half the batch done. The status-change tool is the one worth planning around: on Fider, responding to a post is a public act with a status attached, so it is not the same class of operation as editing a tag.
What it is
A Fider client covering the three objects a feedback board is made of: posts, comments and tags, with 16 tools spanning read, write and moderation.
What you get
- Posts read without authentication and are created with it; editing and deleting need a collaborator or admin role, and each tool states which.
- respond_to_post changes a post's status, which on a Fider board is the act of answering the community rather than a metadata edit.
- Comments have the full lifecycle with ownership enforced — update and delete require that you wrote it, or that you are an admin.
- Tags can be created, edited and deleted by an admin, and assigned or unassigned to posts by a collaborator.
Requirements
FIDER_BASE_URL and FIDER_API_KEY — the base URL because Fider is self-hosted, so there is no default instance to assume.
Setup effort
One command — uvx --from git+https://github.com/ringostat/fider-mcp.git mcp-fider
USE CASES
01
Reading what the board is asking for
List posts with filters and open the ones that matter, along with their comment threads — the read path needs no credentials.
02
Answering the community
Change a post's status, which is how Fider records an official response, and leave the comment that explains it.
03
Getting the board organised
Create the tags the board actually needs and assign them across the posts, instead of tagging one at a time in the web UI.
04
Filing something on behalf of a user
Create the post from the conversation you are already in, then edit it as the details firm up.
16 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
assign_tag
Assign a tag to a post (requires collaborator/admin role)
create_post
Create a new post (requires authentication)
create_tag
Create a new tag (requires admin role)
delete_comment
Delete a comment (requires authentication and ownership/admin)
delete_post
Delete a post (requires admin role)
delete_tag
Delete a tag (requires admin role)
edit_post
Edit an existing post (requires collaborator/admin role)
get_post
Get a specific post by its number
list_comments
List comments for a specific post
list_posts
List posts from Fider with optional filtering
list_tags
List all available tags
respond_to_post
Respond to a post by changing its status (requires collaborator/admin role)
unassign_tag
Unassign a tag from a post (requires collaborator/admin role)
update_comment
Update a comment (requires authentication and ownership)
update_tag
Update an existing tag (requires admin role)
BEFORE YOU INSTALL
What to know first
Tools you get
16 tools when we connected. Ten tools write. Without an API key you can only read; an ordinary key creates posts and comments, and delete_post and tag management need admin.
Requires
uvx on PATH
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 16 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
uvx --from git+https://github.com/ringostat/fider-mcp.git mcp-fiderMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"fider": {
"command": "uvx",
"args": [
"--from",
"mcp-fider==2025.06.27.170000",
"--refresh-package",
"mcp-fider",
"mcp-fider"
],
"env": {
"FIDER_BASE_URL": "<YOUR_FIDER_BASE_URL>",
"FIDER_API_KEY": "<YOUR_FIDER_API_KEY>"
}
}
}
}
