Grasp — Codebase Analysis & Architecture Intelligence vs Jshookmcp

A side-by-side look at the Grasp — Codebase Analysis & Architecture Intelligence and Jshookmcp MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Grasp — Codebase Analysis & Architecture Intelligence logoGrasp — Codebase Analysis & Architecture IntelligenceDeveloper Tools · Local subprocess (stdio)Codebase dependency analysis for LLMs — graphs, architecture, security, refactor, git history.57GoodAuth: not declaredJshookmcp logoJshookmcpDeveloper Tools · Local subprocess (stdio)MCP server for JavaScript analysis, security auditing, browser automation and hooks52GoodAuth: not declared

Verdict: choose Grasp — Codebase Analysis & Architecture Intelligence for developer tools work as a local process; choose Jshookmcp 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?

Grasp — Codebase Analysis & Architecture Intelligence logoChoose Grasp — Codebase Analysis & Architecture Intelligence when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: GRASP_HTTP_MCP.
  • You want tools like grasp_analyze, grasp_sessions, grasp_diff.
Explore Grasp — Codebase Analysis & Architecture Intelligence

Jshookmcp logoChoose Jshookmcp when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
Explore Jshookmcp

Feature & specification comparison

Rows where the two servers differ are marked.

SpecGrasp — Codebase Analysis & Architecture Intelligence logoGrasp — Codebase Analysis & Architecture IntelligenceJshookmcp logoJshookmcp
CategoryDeveloper ToolsDeveloper Tools
Quality signal57/100 · Good52/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsGRASP_HTTP_MCPNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars302,060
Directory activity 2 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools80Not listed

Tools & capabilities

Grasp — Codebase Analysis & Architecture Intelligence tools 80

  • grasp_analyzeFull analysis of any repo or local path — returns `session_id` for follow-up queries
  • grasp_sessionsList active sessions (persist 7 days, survive restarts)
  • grasp_diffCompare two snapshots — what changed between analyses?
  • grasp_watchRe-analyse a directory and diff against a prior run
  • grasp_rules_checkRun `grasp.yml` architecture rules and report violations
  • grasp_config_checkValidate a session against architecture rules — returns violations
  • grasp_file_depsWhat does this file depend on?
  • grasp_dependentsWhat breaks if I change this file?
  • grasp_cyclesAre there circular dependencies?
  • grasp_architectureWhat layers does this codebase have?
  • grasp_hotspotsWhich files are riskiest to touch?
  • grasp_metricsLines, complexity, fan-in/fan-out per file
  • +68 more on the listing page

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

Grasp — Codebase Analysis & Architecture Intelligence

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "grasp-codebase-analysis-architecture-intelligence": {
      "command": "npx",
      "args": [
        "-y",
        "grasp-mcp-server"
      ],
      "env": {
        "GRASP_HTTP_MCP": "YOUR_GRASP_HTTP_MCP_HERE"
      }
    }
  }
}

Jshookmcp

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "jshookmcp": {
      "command": "npx",
      "args": [
        "-y",
        "@jshookmcp/jshook@latest"
      ]
    }
  }
}

Frequently asked questions

Grasp — Codebase Analysis & Architecture Intelligence is categorized under Developer Tools and uses a local stdio subprocess. Jshookmcp belongs to Developer Tools and uses a local stdio subprocess. Pick Grasp — Codebase Analysis & Architecture Intelligence for developer tools work and Jshookmcp 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.

Grasp — Codebase Analysis & Architecture Intelligence has no declared pricing — check the project's own site. Jshookmcp 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 grasp-codebase-analysis-architecture-intelligence and jshookmcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Grasp — Codebase Analysis & Architecture Intelligence has a quality signal of 57/100 (Good) with 2 views, 0 installs and 30 GitHub stars. Jshookmcp has 52/100 (Good) with 2 views, 0 installs and 2,060 GitHub stars.