What is the key difference between Job card and Autotask?

Job card belongs to the Support & Service Management category with local stdio execution, while Autotask belongs to the Support & Service Management category with local stdio execution.

How do I install Job card or Autotask in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Job card and Autotask free or paid?

Job card operates under a Free / Open Source model (No auth required). Autotask operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Job card lists 10 tools with 1 views and 0 GitHub stars. Autotask lists 30 tools with 1 views and 57 GitHub stars.

Can I use both Job card and Autotask together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Job card vs Autotask

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

At a Glance & Executive Verdict

Job card

Support & Service Management · Local stdio

Quality: 52/100 (Good) | Auth: No auth required

Autotask

Support & Service Management · Local stdio

Quality: 56/100 (Good) | Auth: No auth required

Verdict Summary: Choose Job card if you need specialized Support & Service Management tools running via a local process. Choose Autotask if your workspace requires Support & Service Management integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

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 Autotask 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).
You have access to required keys: AUTOTASK_USERNAME, AUTOTASK_SECRET, AUTOTASK_INTEGRATION_CODE.
Primary tools included: autotask_search_companies, autotask_create_company, autotask_update_company.

Feature & Specification Comparison

Specification	J Job card Support & Service Management	Autotask Support & Service Management
Summary	Job cards for trades and field service: hours and materials per job, open to invoiced.	MCP server for Kaseya Autotask PSA — companies, tickets, projects, time entries, and more.
Category & Scope	Support & Service Management	Support & Service Management

Tools & Capabilities Breakdown

Job card Tools (10)

job_card_create

Open a job card: client, site, what the job is, currency, scheduled date. Returns `JC-YYYY-NNNN

job_card_log_labor

Log hours on a job card: who did the work, the day, the hours, the hourly rate in cents, what was done

job_card_log_material

Log materials used on a job card: the item, the quantity, the unit cost in cents

job_card_update_status

Move the card exactly one step -- open, in_progress, done, invoiced, archived -- stamping date and note into its history

job_card_list

List cards newest first with hours and totals; filter by status and client; totals kept per currency

job_card_get

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).

Job card Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "job-card": {
      "command": "npx",
      "args": [
        "-y",
        "@theluckystrike/mcp-job-card"
      ]
    }
  }
}

Autotask Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "autotask": {
      "command": "npx",
      "args": [
        "-y",
        "github:WYRE-AI/autotask-mcp"
      ],
      "env": {
        "AUTOTASK_USERNAME": "YOUR_AUTOTASK_USERNAME_HERE",
        "AUTOTASK_SECRET": "YOUR_AUTOTASK_SECRET_HERE",
        "AUTOTASK_INTEGRATION_CODE": "YOUR_AUTOTASK_INTEGRATION_CODE_HERE"
      }
    }
  }
}

Frequently Asked Questions

Job card is categorized under Support & Service Management and uses a local stdio subprocess. In contrast, Autotask belongs to Support & Service Management using local stdio subprocess. Select Job card when you need capabilities focused on support & service management and Autotask when you require tools for support & service management.