What is the key difference between Statuscraft and Retro?

Statuscraft belongs to the Monitoring category with local stdio execution, while Retro belongs to the Monitoring category with cloud HTTP/SSE execution.

How do I install Statuscraft or Retro in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Statuscraft and Retro free or paid?

Statuscraft operates under a Free / Open Source model (No auth required). Retro operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Statuscraft lists 5 tools with 1 views and 1 GitHub stars. Retro lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Statuscraft and Retro together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

How do I install Statuscraft or Retro in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are Statuscraft and Retro free to use, or do they require API keys?

Statuscraft is listed under a Free / Open Source model with No auth required . Retro operates under a Free / Open Source model with No auth required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both Statuscraft and Retro at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both jabbawocky-statuscraft and retro as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Statuscraft has a Quality Score of 55 /100 ( Good ) with 1 views, 0 installs, and 1 GitHub stars. Retro holds a Quality Score of 42 /100 ( Fair ) with 0 views, 0 installs, and 0 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Statuscraft vs Retro

In-depth architectural comparison of the Statuscraft and Retro MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Statuscraft

Monitoring · Local stdio

Quality: 55/100 (Good) | Auth: No auth required

Retro

Monitoring · Remote HTTP/SSE

Quality: 42/100 (Fair) | Auth: No auth required

Verdict Summary: Choose Statuscraft if you need specialized Monitoring tools running via a local process. Choose Retro if your workspace requires Monitoring integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Statuscraft when:

You need dedicated capabilities in the Monitoring domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Access normalized live status for 3355 major software services, Fetch structured incident details automatically for non-operational services, Cache status data with 60-second expiry and option to bypass cache.

Explore Statuscraft Details

Choose Retro when:

You need dedicated capabilities in the Monitoring domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Retro Details

Feature & Specification Comparison

Specification	Statuscraft jabbawocky Monitoring	R Retro Monitoring
Summary	MCP server that checks the live status of 3831 software services in real time. Ask your AI agent "is GitHub down?" or "what's wrong with Sentry?" — and get a live answer pulled directly from official status pages, including full incident detail when something is broken. npx -y github:jabbawocky/statuscraft	Access QRetro team retrospectives over MCP: boards, summaries, action items, signals, metrics.
Category & Scope	Monitoring

Tools & Capabilities Breakdown

Statuscraft Tools (5)

Access normalized live status for 3355 major software services

Fetch structured incident details automatically for non-operational services

Cache status data with 60-second expiry and option to bypass cache

Provide service metadata including IDs, tags, and categories

No API key required for installation and usage

Retro Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Statuscraft Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "jabbawocky-statuscraft": {
      "command": "npx",
      "args": [
        "-y",
        "github"
      ]
    }
  }
}

Retro Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "retro": {
      "url": "https://qretro.com"
    }
  }
}

Frequently Asked Questions

Statuscraft is categorized under Monitoring and uses a local stdio subprocess. In contrast, Retro belongs to Monitoring using remote streaming HTTP/SSE transport. Select Statuscraft when you need capabilities focused on monitoring and Retro when you require tools for monitoring.

More alternatives to Statuscraft More alternatives to Retro Monitoring category hub