Campus Copilot MCP vs Zoxide Doctor

In-depth architectural comparison of the Campus Copilot MCP and Zoxide Doctor 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 Campus Copilot 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).

Explore Campus Copilot MCP Details

Choose Zoxide Doctor 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).

Explore Zoxide Doctor Details

Feature & Specification Comparison

Specification	Campus Copilot MCP Developer Tools	Zoxide Doctor Developer Tools
Summary	Read-only MCP server for the local Campus Copilot BFF and imported workspace snapshots.	Read-only local zoxide diagnostics for MCP clients.
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": {
    "campus-copilot-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "campus-copilot-mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "zoxide-doctor": {
      "command": "npx",
      "args": [
        "-y",
        "@agoes/zoxide-doctor-mcp"
      ]
    }
  }
}

Related MCP Server Comparisons