AI Context vs Corpus

In-depth architectural comparison of the AI Context and Corpus 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.

Which MCP Server Should You Choose?

Choose AI Context when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: orient, search_symbols, query_graph.

Explore AI Context Details

C

Choose Corpus when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: search_corpus, get_entry, get_passage.

Explore Corpus Details

Feature & Specification Comparison

Specification	AI Context Developer Tools	C Corpus Developer Tools
Summary	Local-first MCP server: version-correct library docs, code map, and offline drift for your repo.	Read-only Wheel of Heaven corpus: myth search, primary texts, datasets, typed graph. CC0.
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

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

{
  "mcpServers": {
    "ai-context": {
      "command": "npx",
      "args": [
        "-y",
        "@vibgrate/cli"
      ]
    }
  }
}

{
  "mcpServers": {
    "corpus-2": {
      "command": "npx",
      "args": [
        "-y",
        "@wheelofheaven/mcp"
      ]
    }
  }
}

Related MCP Server Comparisons