Customer-hosted read-only MCP server for Jobber ops reports, OAuth setup, and GraphQL validation.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-opsconduit-jobber-mcp": {
"args": [
"-y",
"opsconduit-jobber-auth"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Read-only MCP connector for Jobber field-service operations.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'opsconduit-jobber-auth' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked opsconduit-jobber-auth against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in security
Proof primitive for AI agents on MultiversX. Anchor file hashes on-chain as verifiable proofs.
Model Context Protocol for WinDBG
Security scanner for GitHub repos, Agent Skills, Plugins, and MCP servers. 18 scanners. Zero dependencies.
MCP server for Atomic Red Team
MCP Security Weekly
Get CVE alerts and security updates for io.github.opsconduit/jobber-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Read-only MCP connector for Jobber field-service operations.
OpsConduit helps owners and operators ask practical questions about the tools that run their business. This first connector is for Jobber and is designed to stay read-only by default.
Plain buyer-facing overview: docs/index.md. Common buyer questions are answered in docs/faq.md. Example owner/operator prompts are in docs/operator-prompts.md. First paid-install deliverable shape: docs/first-report.md.
More buyer-facing examples are in docs/use-cases.md.
A fictional sample output is available in docs/demo-output.md, or run:
npm run demo
The paid pilot handoff format is documented in docs/pilot-deliverable-template.md.
Early-access pricing is documented in docs/offer.md.
For pilot setup, email opsconduit@gmail.com with the subject Jobber pilot. Do not send Jobber passwords, tokens, API secrets, or private customer data by email.
Requires Node.js 20+.
mkdir opsconduit-jobber
cd opsconduit-jobber
npm install @opsconduit/jobber-mcp
cp node_modules/@opsconduit/jobber-mcp/.env.example .env
npx opsconduit-jobber-auth
npx opsconduit-jobber-mcp
Fill JOBBER_CLIENT_ID and JOBBER_CLIENT_SECRET in .env before running the auth helper. The helper prints a Jobber OAuth URL, receives the local callback at http://localhost:3333/oauth/callback, and stores tokens in .opsconduit/jobber-tokens.json.
Detailed setup notes are in docs/install.md. Paid pilot validation steps are in docs/pilot-checklist.md. Implementation notes for Jobber's GraphQL API are in docs/jobber-api-notes.md.
jobber_auth_url - create the one-time Jobber OAuth authorization link for a customer-hosted install.jobber_exchange_code - exchange the redirected OAuth code and store tokens locally without exposing them in chat.jobber_refresh_token - refresh the stored access token for continued read-only reporting.jobber_account - validate the connected account before running operational queries.jobber_clients_sample - validate read access with a capped client sample.jobber_graphql_read - run read-only Jobber GraphQL for owner reports; mutations are blocked before sending.This repository is in early implementation. The first usable target is a customer-hosted MCP server with local OAuth setup and read-only Jobber GraphQL access.