Project Context MCP vs Vocenya Docs

In-depth architectural comparison of the Project Context MCP and Vocenya Docs 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 Project Context MCP 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: Recursive .context/ file discovery, MCP resource exposure, Claude Code @ mention selection.

Explore Project Context MCP Details

V

Choose Vocenya Docs when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: search_docs, get_doc_page, list_endpoints.

Explore Vocenya Docs Details

Feature & Specification Comparison

Specification	Project Context MCP ericbrown Developer Tools	V Vocenya Docs VerifiedDeveloper Tools
Summary	Exposes .context/ folder files as MCP resources, giving Claude Code instant access to project documentation via @ mentions.	Public, read-only MCP server for the Vocenya API docs: search guides, read pages and get every REST endpoint with cURL, Node, PHP and Python samples.
Category & Scope

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": {
    "ericbrown-project-context-mcp": {
      "command": "uvx",
      "args": [
        "project-context-mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "vocenya-docs": {
      "url": "https://vocenya.com/mcp/docs"
    }
  }
}

Related MCP Server Comparisons