Log inSubmit server

CrashStory MCP vs Codegraphcontext

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

C
CrashStory MCPLegal · Remote HTTP/SSEColorado personal injury attorney directory, AI-analyzed review intelligence, and crash data42FairAuth: not declaredCodegraphcontext logoCodegraphcontextDeveloper Tools · Local subprocess (stdio)An MCP server that indexes local code into a graph database to provide context to AI assistants with a graphical code visualizations for humans.59GoodAuth: no auth required

Verdict: choose CrashStory MCP for legal work over a hosted endpoint; choose Codegraphcontext for developer tools as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

C
Choose CrashStory MCP when

  • You need dedicated capabilities in the Legal domain.
  • You prefer a remote HTTP/SSE transport.
Explore CrashStory MCP

Codegraphcontext logoChoose Codegraphcontext when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
Explore Codegraphcontext

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
C
CrashStory MCP		Codegraphcontext logoCodegraphcontext
CategoryLegalDeveloper Tools
Quality signal42/100 · Fair59/100 · Good
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—4,352
Directory activity 1 views 0 installs 0 upvotes 5 views 0 installs 0 upvotes
ToolsNot listedNot listed
Full listingView CrashStory MCP View Codegraphcontext

Tools & capabilities

CrashStory MCP tools

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

Codegraphcontext 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.

CrashStory MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "crashstory-mcp": {
      "url": "https://crashstory.com/mcp"
    }
  }
}

Codegraphcontext

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "shashankss1205-codegraphcontext": {
      "command": "uvx",
      "args": [
        "kuzu"
      ]
    }
  }
}

Frequently asked questions

CrashStory MCP is categorized under Legal and uses a remote HTTP/SSE transport. Codegraphcontext belongs to Developer Tools and uses a local stdio subprocess. Pick CrashStory MCP for legal work and Codegraphcontext for developer tools.

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.

CrashStory MCP has no declared pricing — check the project's own site. Codegraphcontext is listed as free. Auth: no auth required. 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 crashstory-mcp and shashankss1205-codegraphcontext as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, CrashStory MCP has a quality signal of 42/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Codegraphcontext has 59/100 (Good) with 5 views, 0 installs and 4,352 GitHub stars.

Popular comparisons with CrashStory MCP

Popular comparisons with Codegraphcontext