Feedbucket MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FEEDBUCKET_API_KEY | No | API key for protected projects (feedbucketKey from URL). Required if your project uses query string protection. | |
| FEEDBUCKET_PROJECT_ID | Yes | Project ID from the data-feedbucket attribute | |
| FEEDBUCKET_PRIVATE_KEY | Yes | Private key for commenting/resolving (auto-fetched by setup) |
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 |
|---|---|
| feedback_listA | Fetch all feedback items from the Feedbucket project with intelligent filtering for AI consumption. Automatically optimizes data to prevent overwhelming responses. Each feedback item may include a screenshot URL in the "resource" field - use feedback_get to retrieve full details and view the screenshot for visual context. |
| feedback_commentC | Add a comment to a specific feedback item to ask for clarification or provide updates |
| feedback_resolveC | Mark a feedback item as resolved after actioning it |
| feedback_getA | Get full details of a specific feedback item including all comments, attachments, and session data. IMPORTANT: For screenshot feedback, the response includes a "resource" field with the screenshot URL. You should download this image to a temporary file and view it to see the visual context including the green dot showing where the user clicked. The screenshot provides crucial context for understanding the feedback. |
| feedback_statsA | Get a quick summary of project feedback statistics - total count, resolved/unresolved breakdown, feedback by type, and recent activity |
| api_statusB | Check Feedbucket API connection status and configuration |
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 6 tools
Each tool has a clearly distinct purpose with no overlap: api_status checks connectivity, feedback_comment adds comments, feedback_get retrieves details, feedback_list fetches items, feedback_resolve marks items as resolved, and feedback_stats provides summaries. The tools target different actions on the feedback resource, making misselection unlikely.
All tools follow a consistent verb_noun pattern with 'feedback_' prefix for feedback-related operations (e.g., feedback_comment, feedback_get) and 'api_' for the status check. This predictable naming scheme enhances readability and agent usability.
With 6 tools, the server is well-scoped for managing feedback in a Feedbucket project. Each tool earns its place by covering essential operations like listing, getting, commenting, resolving, and checking stats, plus an API status tool, without being overwhelming or insufficient.
The tool set provides complete CRUD/lifecycle coverage for feedback management: list (feedback_list), read (feedback_get), update (feedback_comment, feedback_resolve), and delete is implied through resolution. Additional tools for stats and API status enhance functionality, leaving no obvious gaps for agents to handle feedback workflows.