Repocrunch vs Super Log

A side-by-side look at the Repocrunch and Super Log MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Repocrunch logoRepocrunchMonitoring · Local subprocess (stdio)MCP server that gives AI agents structured, ground-truth GitHub repository intelligence. Analyze tech stack, dependencies, architecture, health metrics, and security indicators with deterministic JSON output.47FairAuth: not declaredSuper Log logoSuper LogMonitoring · Local subprocess (stdio)Query your local super-log bench from an AI agent - read-only log tools over the hub.44FairAuth: not declared

Verdict: choose Repocrunch for monitoring work as a local process; choose Super Log for monitoring as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Repocrunch logoChoose Repocrunch when

  • You need dedicated capabilities in the Monitoring domain.
  • You prefer a local stdio subprocess transport.
Explore Repocrunch

Super Log logoChoose Super Log when

  • You need dedicated capabilities in the Monitoring domain.
  • You prefer a local stdio subprocess transport.
Explore Super Log

Feature & specification comparison

Rows where the two servers differ are marked.

SpecRepocrunch logoRepocrunchSuper Log logoSuper Log
CategoryMonitoringMonitoring
Quality signal47/100 · Fair44/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars91
Directory activity 2 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Repocrunch tools

No tool names declared yet. Check the project README from the listing page.

Super Log tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Repocrunch

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "kimwwk-repocrunch": {
      "command": "uvx",
      "args": [
        "repocrunch"
      ]
    }
  }
}

Super Log

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "super-log": {
      "command": "npx",
      "args": [
        "-y",
        "@super-log/mcp"
      ]
    }
  }
}

Frequently asked questions

Repocrunch is categorized under Monitoring and uses a local stdio subprocess. Super Log belongs to Monitoring and uses a local stdio subprocess. Pick Repocrunch for monitoring work and Super Log for monitoring.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Repocrunch has no declared pricing — check the project's own site. Super Log has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add kimwwk-repocrunch and super-log as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Repocrunch has a quality signal of 47/100 (Fair) with 2 views, 0 installs and 9 GitHub stars. Super Log has 44/100 (Fair) with 1 views, 0 installs and 1 GitHub stars.