Sitelemetry vs Depwire

In-depth architectural comparison of the Sitelemetry and Depwire 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?

S

Choose Sitelemetry 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: audit_security, audit_seo, audit_ai_visibility.

Explore Sitelemetry Details

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

Feature & Specification Comparison

Specification	S Sitelemetry Developer Tools	Depwire depwire Developer Tools
Summary	OAuth website audits: security, SEO, AI visibility, integrations, accessibility and performance.	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.
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": {
    "sitelemetry-2": {
      "url": "https://sitelemetry.com/mcp"
    }
  }
}

{
  "mcpServers": {
    "depwire-depwire": {
      "command": "npx",
      "args": [
        "-y",
        "depwire-cli"
      ]
    }
  }
}

Related MCP Server Comparisons