gripe-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@gripe-mcpLog an issue: the 'plot' tool documentation is missing parameter descriptions."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
gripe-mcp
Agent complaint box — one-tool MCP for logging bugs and improvement requests.
One tool: report_issue
Call it when you guess, hit a missing tool, find bad docs, or produce uncertain output. Non-blocking — log and continue.
Param | Type | Description |
| str | What went wrong or what you'd like improved (max 200 chars) |
|
| low = friction, medium = guessed, high = abandoned/wrong |
| str | Which instruction or tool caused the issue (max 80 chars) |
| enum |
|
Storage
Postgres: set
GRIPE_DB_URLenv var → singlegripe_issuestableJSONL fallback: timestamped files in
.gripe-mcp/(one per day)
Identity
GRIPE_AGENT_ID and GRIPE_TASK_ID are set at server startup via env vars.
The agent never self-reports identity.
System prompt block
## Self-Monitoring
Use `report_issue` any time you guess, hit a missing tool, or produce output
you're uncertain about. Non-blocking — log and continue, no response expected.
There is no penalty for logging; silence is the failure mode we're trying to
prevent.Run
GRIPE_AGENT_ID=precis GRIPE_TASK_ID=review-123 gripeMaintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Tools
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/retospect/gripe-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server