Jobber MCP Server vs STEADYWRK Field Service Dispatch
A side-by-side look at the Jobber MCP Server and STEADYWRK Field Service Dispatch MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
STEADYWRK Field Service DispatchSupport & Service Management · Remote HTTP/SSEField service dispatch: instant quotes, tracked work orders, public evals. steadywrk.app37FairAuth: not declaredVerdict: choose Jobber MCP Server for support & service management work as a local process; choose STEADYWRK Field Service Dispatch for support & service management over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Jobber MCP Server when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
JOBBER_ACCESS_TOKEN, JOBBER_CLIENT_ID, JOBBER_CLIENT_SECRET. - You want tools like
list_clients, get_client, get_job.
SChoose STEADYWRK Field Service Dispatch when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S STEADYWRK Field Service Dispatch | |
|---|---|---|
| Category | Support & Service Management | Support & Service Management |
| Quality signal | 36/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | JOBBER_ACCESS_TOKENJOBBER_CLIENT_IDJOBBER_CLIENT_SECRET | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | — |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 6 | Not listed |
| Full listing | View Jobber MCP Server | View STEADYWRK Field Service Dispatch |
Tools & capabilities
Jobber MCP Server tools 6
list_clientsList clients with optional search, lead filter, and limitget_clientGet a client by ID with contact info and recent jobsget_jobFull job detail: status, assignees, schedule, line itemslist_invoicesList invoices filtered by client and/or statusget_invoiceFull invoice detail with line items and payment statuscreate_quoteCreate a new quote for a client with line items
STEADYWRK Field Service Dispatch tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Jobber MCP Server
{
"mcpServers": {
"jobber-mcp-server": {
"command": "npx",
"args": [
"-y",
"jobber-mcp-server"
],
"env": {
"JOBBER_ACCESS_TOKEN": "YOUR_JOBBER_ACCESS_TOKEN_HERE",
"JOBBER_CLIENT_ID": "YOUR_JOBBER_CLIENT_ID_HERE",
"JOBBER_CLIENT_SECRET": "YOUR_JOBBER_CLIENT_SECRET_HERE"
}
}
}
}
STEADYWRK Field Service Dispatch
{
"mcpServers": {
"steadywrk-field-service-dispatch": {
"url": "https://steadywrk.app/developers/mcp"
}
}
}
Frequently asked questions
Jobber MCP Server is categorized under Support & Service Management and uses a local stdio subprocess. STEADYWRK Field Service Dispatch belongs to Support & Service Management and uses a remote HTTP/SSE transport. Pick Jobber MCP Server for support & service management work and STEADYWRK Field Service Dispatch for support & service management.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Jobber MCP Server has no declared pricing — check the project's own site. STEADYWRK Field Service Dispatch has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add jobber-mcp-server and steadywrk-field-service-dispatch as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Jobber MCP Server has a quality signal of 36/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. STEADYWRK Field Service Dispatch has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.