Jobkeepr
Manage jobs, customers, scheduling, estimates and invoices for a field service business.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http jobkeepr 'https://jobkeepr.com/mcp'{
"mcpServers": {
"jobkeepr": {
"type": "http",
"url": "https://jobkeepr.com/mcp"
}
}
}Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
Jobkeepr MCP server
Connect Jobkeepr to Claude, ChatGPT, or any other MCP client, so an AI assistant can read and manage your field service business: jobs, customers, scheduling, estimates, invoices and payments.
Jobkeepr is field service management software for small contractor crews — handymen, TV installers, plumbers, electricians, HVAC techs — running one to ten people.
"What's on my schedule tomorrow?"
"Which service made me the most money last month?"
"Book Sarah Chen for a TV mount Thursday at 2pm."
"Mark today's jobs complete."Two ways to connect
Remote (recommended). If your client supports remote MCP servers, point it straight at the hosted endpoint and skip this package entirely:
https://jobkeepr.com/mcpIt supports OAuth, so you sign in with your normal Jobkeepr login and approve access in the browser. Nothing to install.
stdio (this package). For clients that only speak stdio, this bridges to the same server using an API key.
This package is not on npm. Install it straight from GitHub using the
github:dandyer/jobkeepr-mcpspecifier shown below. Plainnpx jobkeepr-mcpwill not resolve. npm compiles the TypeScript for you on install, so there is nothing extra to run.
Setup
Create an API key in Jobkeepr under Settings → API Keys. It's shown once, so copy it then.
Claude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"jobkeepr": {
"command": "npx",
"args": ["-y", "github:dandyer/jobkeepr-mcp"],
"env": {
"JOBKEEPR_API_KEY": "jk_live_your_key_here"
}
}
}
}Claude Code
claude mcp add jobkeepr --env JOBKEEPR_API_KEY=jk_live_your_key_here -- npx -y github:dandyer/jobkeepr-mcpOr connect to the remote endpoint directly:
claude mcp add --transport http jobkeepr https://jobkeepr.com/mcpTools
Reading
| Tool | What it does |
|---|---|
get_business_context | Business name, timezone, working hours, and today's date with resolved ranges for "this week", "last month" and so on |
get_jobs | Jobs filtered by date, status, customer, type or source |
get_customers | Search customers, optionally with job counts and totals |
get_schedule | Scheduled jobs, calendar events, and open time slots |
get_estimates | Estimates and their status |
get_invoices | Invoices and unpaid balances |
get_payments | Payments received |
get_line_items | Line items across jobs, for margin and mix analysis |
get_reference_data | Job types, lead sources, and the price catalog |
Writing
| Tool | What it does |
|---|---|
create_job | Book a job for a customer |
create_event | Add a calendar event that is not a job, like time off or a walkthrough |
create_customer | Add a customer |
create_estimate | Create an estimate |
create_catalog_item | Add a service or product to the price catalog |
add_line_items | Add billable line items to a job |
set_customer_source | Record how a customer found the business |
reschedule_job | Move a job to a new date or time |
cancel_job | Cancel a scheduled job |
close_jobs | Mark jobs complete |
The financial tools require the VIEW_FINANCIALS permission, and each write tool requires its matching permission. Tools you cannot use are not listed to you.
What it will not do
No tool here can text your customers. Sending SMS is deliberately excluded: it is the one action that reaches a real person and cannot be undone. Ask your assistant to draft a message and send it yourself from Jobkeepr.
Writes take effect immediately. There is no staging step and no undo, which is why cancel_job and close_jobs are marked destructive so your client prompts before running them. close_jobs can act on many jobs at once, so check the set before approving it.
Configuration
| Variable | Required | Default | Notes |
|---|---|---|---|
JOBKEEPR_API_KEY | yes | — | From Settings → API Keys. Starts with jk_live_. |
JOBKEEPR_URL | no | https://jobkeepr.com | Override only for self-hosted or staging. |
An API key acts on one account and carries owner-level access. Revoke it any time in Settings → API Keys. To give an assistant narrower, per-user access instead, use the remote endpoint with OAuth.
How it works
This package is a proxy, not a reimplementation. The tools live on the hosted server; this bridges stdio to it. That means the tool set here is always current and this package rarely needs a release.
Development
npm install
npm run build
JOBKEEPR_API_KEY=jk_live_... node dist/index.jsTest interactively with the MCP Inspector:
JOBKEEPR_API_KEY=jk_live_... npx @modelcontextprotocol/inspector node dist/index.jsLinks
MIT licensed.
Frequently asked questions
What is Jobkeepr?
Manage jobs, customers, scheduling, estimates and invoices for a field service business.
How do I install Jobkeepr?
It runs as a remote server. In Claude Code: claude mcp add --transport http jobkeepr 'https://jobkeepr.com/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Jobkeepr need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is Jobkeepr open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains Jobkeepr?
It is published by dandyer. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.