Job card vs Fieldproxy

In-depth architectural comparison of the Job card and Fieldproxy 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?

J

Choose Job card when:

• You need dedicated capabilities in the Support & Service Management domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: job_card_create, job_card_log_labor, job_card_log_material.

Explore Job card Details

Choose Fieldproxy when:

• You need dedicated capabilities in the Support & Service Management domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• You have access to required keys: FIELDPROXY_MCP_KEY.
• Primary tools included: Field-service records and read-only SQL, Dispatch, routes, technicians, and job sign-offs, Confirmed writes with undo and audit logging.

Feature & Specification Comparison

Specification	J Job card Support & Service Management	Fieldproxy Support & Service Management
Summary	Job cards for trades and field service: hours and materials per job, open to invoiced.	Field service management: jobs, dispatch, invoices, quotes and building apps, confirm before change.
Category & Scope	Support & Service Management	Support & Service Management

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": {
    "job-card": {
      "command": "npx",
      "args": [
        "-y",
        "@theluckystrike/mcp-job-card"
      ]
    }
  }
}

{
  "mcpServers": {
    "fieldproxy": {
      "url": "https://www.fieldproxy.ai/mcp"
    }
  }
}

Related MCP Server Comparisons