Invoice Intake (reference) vs MCP Graphql

In-depth architectural comparison of the Invoice Intake (reference) and MCP Graphql 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?

I

Choose Invoice Intake (reference) 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 Invoice Intake (reference) Details

Choose MCP Graphql 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: introspect-schema, query-graphql.

Explore MCP Graphql Details

Feature & Specification Comparison

Specification	I Invoice Intake (reference) Developer Tools	MCP Graphql blurrah Developer Tools
Summary	Reference invoice-intake MCP servers: read/draft/commit split, typed errors, approval gate, audit	Model Context Protocol server for GraphQL
Category & Scope	Developer Tools	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": {
    "invoice-intake-reference": {
      "command": "npx",
      "args": [
        "-y",
        "invoice-intake-reference"
      ]
    }
  }
}

{
  "mcpServers": {
    "blurrah-mcp-graphql": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-graphql"
      ]
    }
  }
}

Related MCP Server Comparisons