Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
JarvisOnM4 avatar

Report Needs MCP Server

  • Updated April 8, 2026
  • JarvisOnM4/report-needs

Report Needs is an MCP server that lets AI agents record infrastructure gaps they discover while running tasks.

About

Report Needs is a Model Context Protocol server that lets coding agents formally report infrastructure requirements they encounter while executing tasks—missing APIs, unprovisioned services, credential gaps, or environment misconfigurations—instead of burying those blockers in conversational noise. developers running long agent sessions in Claude Code or Cursor benefit because one person cannot watch every tool failure; structured reports become a backlog input for Operate and Build follow-ups. Install from PyPI with stdio MCP configuration alongside your other servers. It does not provision cloud resources itself; it documents what your agent needed so you can prioritize infra work. Use it when agents are already doing deploy scripts, integrations, or runbook automation and you want a durable signal channel.

  • MCP tools for agents to report infrastructure needs discovered during execution
  • PyPI package report-needs 0.1.1 with stdio transport
  • Turns transient agent failures into structured need reports
  • Maintained at JarvisOnM4/report-needs on GitHub
  • Lightweight 0.1.x server for agent-driven ops feedback

Report Needs MCP Server by the numbers

  • Data as of Jul 7, 2026 (Skillselion catalog sync)
terminal
claude mcp add report-needs -- uvx report-needs

Add your badge

Show developers this MCP server is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Packagereport-needs
TransportSTDIO
AuthNone
Last updatedApril 8, 2026
RepositoryJarvisOnM4/report-needs

What it does

Capture infrastructure gaps your agent hits mid-task so you can queue real fixes instead of losing context in chat logs.

Who is it for?

Agent-heavy workflows where execution often stalls on env, secrets, or services you still need to provision.

Skip if: Skip if you want automatic cloud provisioning, full incident management, or non-agent manual ticketing only.

What you get

After adding the stdio MCP server, agents can emit structured infrastructure need reports you can turn into a fix queue.

  • Stdio MCP server registered for agent sessions
  • Structured infrastructure need reports from agent runs
  • Actionable backlog items for secrets, services, and environment fixes

By the numbers

  • Published version 0.1.1 on PyPI
  • Transport: stdio MCP
  • Registry identifier: report-needs
README.md

report-needs

MCP Compatible License Smithery

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_DB is optional. Defaults to needs.db in 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

Dashboard screenshot

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

  1. Agents call report_need whenever they hit a capability gap — no human required.
  2. Other agents call vote_need when they encounter the same gap. Votes are deduplicated by voter ID.
  3. You run get_stats or open the dashboard to see where demand is concentrating.
  4. 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

Recommended MCP Servers

How it compares

Agent-to-human infra need reporter via MCP, not a PaaS provisioner or uptime monitor.

FAQ

Who is Report Needs for?

Developers and small teams whose coding agents routinely uncover missing infrastructure during automated tasks.

When should I use Report Needs?

Use it during Operate and late Build when agents execute scripts, integrations, or deploy steps and you want durable records of what blocked them.

How do I add Report Needs to my agent?

Install PyPI package report-needs 0.1.1, add the stdio MCP server entry in your client config, and enable tools so agents can submit need reports during runs.

Developer Toolsinframonitoring

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.