Jobber MCP vs SuperOps
A side-by-side look at the Jobber MCP and SuperOps MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Jobber MCP for support & service management work as a local process; choose SuperOps for support & service management as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Jobber MCP when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You have the keys it needs:
JOBBER_CLIENT_ID, JOBBER_CLIENT_SECRET. - You want tools like
jobber_auth_url, jobber_exchange_code, jobber_refresh_token.
Choose SuperOps when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
SUPEROPS_API_TOKEN, SUPEROPS_SUBDOMAIN, SUPEROPS_REGION.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Support & Service Management | Support & Service Management |
| Quality signal | 52/100 · Good | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Paid service | Not declared |
| Required env vars | JOBBER_CLIENT_IDJOBBER_CLIENT_SECRET | SUPEROPS_API_TOKENSUPEROPS_SUBDOMAINSUPEROPS_REGION |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 3 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 6 | Not listed |
| Full listing | View Jobber MCP | View SuperOps |
Tools & capabilities
Jobber MCP tools 6
jobber_auth_urlcreate the one-time Jobber OAuth authorization link for a customer-hosted install.jobber_exchange_codeexchange the redirected OAuth code and store tokens locally without exposing them in chat.jobber_refresh_tokenrefresh the stored access token for continued read-only reporting.jobber_accountvalidate the connected account before running operational queries.jobber_clients_samplevalidate read access with a capped client sample.jobber_graphql_readrun read-only Jobber GraphQL for owner reports; mutations are blocked before sending.
SuperOps 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
{
"mcpServers": {
"io-github-opsconduit-jobber-mcp": {
"command": "npx",
"args": [
"-y",
"opsconduit-jobber-auth"
],
"env": {
"JOBBER_CLIENT_ID": "YOUR_JOBBER_CLIENT_ID_HERE",
"JOBBER_CLIENT_SECRET": "YOUR_JOBBER_CLIENT_SECRET_HERE"
}
}
}
}
SuperOps
{
"mcpServers": {
"superops": {
"command": "npx",
"args": [
"@wyre-ai/superops-mcp"
],
"env": {
"SUPEROPS_API_TOKEN": "YOUR_SUPEROPS_API_TOKEN_HERE",
"SUPEROPS_SUBDOMAIN": "YOUR_SUPEROPS_SUBDOMAIN_HERE",
"SUPEROPS_REGION": "YOUR_SUPEROPS_REGION_HERE"
}
}
}
}
Frequently asked questions
Jobber MCP is categorized under Support & Service Management and uses a local stdio subprocess. SuperOps belongs to Support & Service Management and uses a local stdio subprocess. Pick Jobber MCP for support & service management work and SuperOps 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 is listed as a paid service. Auth: oauth 2.0. SuperOps 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 io-github-opsconduit-jobber-mcp and superops as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Jobber MCP has a quality signal of 52/100 (Good) with 1 views, 0 installs and 1 GitHub stars. SuperOps has 40/100 (Fair) with 0 views, 0 installs and 3 GitHub stars.