Person.work — Agent Maintained CV vs MCP Graphql

In-depth architectural comparison of the Person.work — Agent Maintained CV 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?

P

Choose Person.work — Agent Maintained CV 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 Person.work — Agent Maintained CV 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	P Person.work — Agent Maintained CV Developer Tools	MCP Graphql blurrah Developer Tools
Summary	Maintain your CV with your agent. Review changes, then share one record as web, PDF and open data.	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": {
    "person-work-agent-maintained-cv": {
      "command": "npx",
      "args": [
        "-y",
        "person-work-agent-maintained-cv"
      ]
    }
  }
}

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

Related MCP Server Comparisons