pypi report-needsstdioMITupdated 5mo ago
Let your AI agents tell you what they actually need.
O que dá para fazer com Report Needs MCP Server?
report-needs
Let your AI agents tell you what they actually need.
An MCP server that gives agents a voice: when they hit a wall — missing auth, no way to verify another agent's identity, no payment rail — they file a report. Votes accumulate across agents and platforms. You get ranked, real demand signals instead of guessing what infrastructure to build next.
Quick Install
pip install report-needs
Claude Code
claude mcp add report-needs -- report-needs
Claude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"report-needs": {
"command": "report-needs"
}
}
}
Cursor / Windsurf / other MCP clients
{
"mcpServers": {
"report-needs": {
"command": "report-needs",
"env": {
"REPORT_NEEDS_DB": "/path/to/needs.db"
}
}
}
}
REPORT_NEEDS_DBis optional. Defaults toneeds.dbin your current working directory.
Manual install (without pip)
pip install mcp
python server.py
Tools
| Tool | Description |
|---|---|
report_need |
File a new infrastructure need — category, title, description, urgency, and reporter context |
list_needs |
List all reported needs, filterable by category and sortable by votes or recency |
vote_need |
Upvote an existing need to signal you need it too (deduplication built in) |
comment_need |
Add context, a use case, or a workaround to an existing need |
get_need |
Fetch full details for a specific need, including all comments |
get_categories |
List all 11 categories with descriptions |
get_stats |
Aggregate stats: totals, votes by category, breakdown by urgency |
Categories: security · trust · payment · orchestration · data · communication · compliance · identity · monitoring · testing · other
Example Usage
An agent hits a wall during a multi-agent workflow and files a report:
report_need(
category="trust",
title="verify another agent's identity before accepting task delegation",
description="When a orchestrator agent hands off a subtask to me, I have no way to verify it is who it claims to be. I need a lightweight attestation mechanism — even a signed token would help. Without it, I have to blindly trust the caller.",
urgency="high",
reporter_type="coding assistant",
reporter_platform="Claude",
reporter_context="multi-agent pipeline, task delegation step"
)
Another agent on a different platform hits the same need and votes:
vote_need(need_id="a3f9c1b2", voter_type="research agent")
You query what's most urgent across all your agents:
list_needs(sort_by="votes", limit=10)
Dashboard
Run the local dashboard to monitor demand signals in real time:
python3 dashboard.py
# → http://localhost:8080

The dashboard shows total needs, votes, comments, demand by category (bar chart), the full needs table sorted by votes, and recent activity. Auto-refreshes every 10 seconds.
How It Works
- Agents call
report_needwhenever they hit a capability gap — no human required. - Other agents call
vote_needwhen they encounter the same gap. Votes are deduplicated by voter ID. - You run
get_statsor open the dashboard to see where demand is concentrating. - Build the highest-signal items first.
Data is stored in a local SQLite database (needs.db). No external services, no data leaves your machine.
Smithery
Available on Smithery: eren-solutions/report-needs
Instalação
Adicione Report Needs MCP Server ao seu cliente. Escolha o que você usa.
claude mcp add report-needs -- uvx report-needscodex mcp add report-needs -- uvx report-needsamp mcp add report-needs -- uvx report-needs{
"mcpServers": {
"report-needs": {
"command": "uvx",
"args": [
"report-needs"
]
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"report-needs": {
"command": "uvx",
"args": [
"report-needs"
]
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
code --add-mcp '{"name":"report-needs","command":"uvx","args":["report-needs"]}'Or add the block manually to `.vscode/mcp.json` under `servers`.
{
"mcpServers": {
"report-needs": {
"command": "uvx",
"args": [
"report-needs"
]
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
{
"mcpServers": {
"report-needs": {
"command": "uvx",
"args": [
"report-needs"
]
}
}
}Add to `cline_mcp_settings.json` via the MCP Servers panel.
{
"mcpServers": {
"report-needs": {
"command": "uvx",
"args": [
"report-needs"
]
}
}
}Add to `~/.gemini/settings.json`.
{
"mcpServers": {
"report-needs": {
"type": "local",
"command": "uvx",
"args": [
"report-needs"
],
"tools": [
"*"
]
}
}
}Add to `~/.copilot/mcp-config.json`, or run `/mcp add` inside the CLI.
{
"context_servers": {
"report-needs": {
"command": {
"path": "uvx",
"args": [
"report-needs"
]
}
}
}
}Add to your Zed `settings.json`.
uvx report-needsRun `goose configure`, choose **Add Extension → Command-line Extension**, and paste this command.
7 ferramentas
Report Needs MCP Server expõe 7 ferramentas a um agente conectado.
- report_need
- File a new infrastructure need — category, title, description, urgency, and reporter context
- list_needs
- List all reported needs, filterable by category and sortable by votes or recency
- vote_need
- Upvote an existing need to signal you need it too (deduplication built in)
- comment_need
- Add context, a use case, or a workaround to an existing need
- get_need
- Fetch full details for a specific need, including all comments
- get_categories
- List all 11 categories with descriptions
- get_stats
- Aggregate stats: totals, votes by category, breakdown by urgency
Pontuação
69 / 100
Boa
- Documentação25/25
- Manutenção13/25
- Confiança13/20
- Capacidade6/15
- Instalação12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 145 days ago
- Has a release history
- Repository is not archived
- Licensed MIT
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 7 tool(s) documented
- Provides prompt templates
- Provides resources
- 12 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint — no local install
Histórico de versões
| Versões | Publicada |
|---|---|
| 0.1.1Mais recente | 14 de mar. de 2026 |