Git vs Jobber MCP Server
A side-by-side look at the Git and Jobber MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Git for version control work as a local process; choose Jobber MCP Server 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 Git when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
repo_path, context_lines, target.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Support & Service Management |
| Quality signal | 81/100 · Excellent | 36/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | JOBBER_ACCESS_TOKENJOBBER_CLIENT_IDJOBBER_CLIENT_SECRET |
| Verified owner | Verified | Community listing |
| GitHub stars | 91,526 | 0 |
| Directory activity | 49 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 16 | 6 |
| Full listing | View Git | View Jobber MCP Server |
Tools & capabilities
Git tools 16
repo_pathcontext_linestargetmessageMERGE_HEADHEADfilesmax_countstart_timestampend_timestampbranch_namebase_branch- +4 more on the listing page
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
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.
Git
{
"mcpServers": {
"git": {
"command": "uvx",
"args": [
"installations"
]
}
}
}
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"
}
}
}
}
Frequently asked questions
Git is categorized under Version Control and uses a local stdio subprocess. Jobber MCP Server belongs to Support & Service Management and uses a local stdio subprocess. Pick Git for version control work and Jobber MCP Server 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.
Git is listed as free. Auth: no auth required. Jobber MCP Server 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 git and jobber-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Git has a quality signal of 81/100 (Excellent) with 49 views, 0 installs and 91,526 GitHub stars. Jobber MCP Server has 36/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.