Depwire vs MCP Contact Classifier

In-depth architectural comparison of the Depwire and MCP Contact Classifier 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 Depwire 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: Deterministic tree-sitter dependency parsing, MCP access to local codebase graph data, What-if impact simulation.

Explore Depwire Details

Choose MCP Contact Classifier 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).
• You have access to required keys: APIFY_TOKEN.
• Primary tools included: classify_contact.

Explore MCP Contact Classifier Details

Feature & Specification Comparison

Specification	Depwire depwire Developer Tools	MCP Contact Classifier Developer Tools
Summary	Dependency graph + 15 MCP tools for AI coding assistants. Parses TypeScript, JavaScript, Python, Go, Rust, and C. Arc diagram visualization, health scoring, dead code detection, and temporal graph.	Classify a job title into department and seniority, and optionally verify the position.
Category & Scope	Developer Tools

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": {
    "depwire-depwire": {
      "command": "npx",
      "args": [
        "-y",
        "depwire-cli"
      ]
    }
  }
}

{
  "mcpServers": {
    "mcp-contact-classifier": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-contact-classifier"
      ],
      "env": {
        "APIFY_TOKEN": "YOUR_APIFY_TOKEN_HERE"
      }
    }
  }
}

Related MCP Server Comparisons