What does tomorrow look like, and who is still unassigned?
list_jobsRead onlylist_techniciansRead only
The owner gets tomorrow’s board in one answer, with the gaps called out.
Connector builds / For field service software
Your dispatch board, from the truck.
A Claude or ChatGPT connector for field service software lets a contractor run the board by asking: what is scheduled tomorrow, who is unassigned, which estimates went quiet, which invoices are past due. Reads answer at once. Creating a job, assigning a tech or converting a lead drafts first and runs only when the owner says yes. ServiceM8, GorillaDesk and Zuper already ship official MCP servers, so the category is moving, and I build yours on your own API.
Nine of our tools are listed in Anthropic’s Claude directory.
At a glance
- Who asks
- Owners in the truck, office managers at the desk
- First tools
- Schedule, jobs, estimates, invoices, leads
- Held for a yes
- Create, assign, reschedule, convert
- Kept out
- Charging cards and refunds
Checked October 12, 2026
What your customers would ask
The jobs they would do in Claude.
Reads answer at once. Anything that changes data drafts first and waits for a yes. Tool names here are illustrative: yours map to the real endpoints in your API docs.
Turn the Henderson lead into a job and put Marco on it Thursday morning.
convert_leadWrite, heldassign_jobWrite, heldconfirm_actionApproval step
Both changes are drafted and shown together; nothing lands on the board until the owner confirms.
Which estimates did we send last month that never got an answer?
list_estimatesRead only
The follow-up list that usually lives in someone’s head.
Which invoices are past 30 days, biggest first?
list_invoicesRead only
Read only. Collecting the money happens in your product, not in the chat.
Design notes for this category
What I design around in field service.
Field service data is messy in ways a model will trip on unless the tools account for it. These are the calls I make up front:
- Names are ambiguous. “The Henderson job” can match three customers, so lookups return candidates and the write tools take an ID, never a name.
- Time zones and crews. A reschedule shows the exact slot in the business’s own time zone and the tech’s existing load before it asks for a yes.
- Money stays in your product. Anthropic’s review criteria do not accept connectors that transfer money, so I build payment jobs as reads and payment-link drafts, never as a charge or a refund.
- Scope by role. A tech who signs in sees their own jobs; the owner sees the board. OAuth scopes follow the permissions you already have.
Why it is worth doing
Short questions, asked all day.
The questions a contractor asks in a day are short and repetitive: who is where, what is late, who owes us. A connector turns those into answers from the system of record instead of a call to the office. For your product, it means the assistant your customer already uses sends them back to your data, many times a day.
The category is moving
Already in the assistants in your category.
These companies publish official MCP servers today. Each line is read from the company’s own page, linked.
ServiceM8
Publishes an official MCP server and a help article on connecting it to ChatGPT.
GorillaDesk
Publishes official MCP server documentation for its API.
Zuper
Markets an official MCP server: “Give Claude, Cursor or your own agent 290 tools.”
- Listed in Anthropic’s Claude directory
- 9
- In review with Anthropic
- 4
- In the official MCP Registry
- 15
- Tools Claude can call
- 69
What we have shipped
Built and running, not a deck.
Owner’s Desk
Our own OAuth 2.1 connector. It reaches the owner’s Stripe and Google accounts, every write waits for a confirm token, and every action lands in an audit log.
AI Front Door
One multi-tenant deploy that gives every business its own connector, white label, under an agency’s brand.
Small Business Agent Bench
Our open benchmark of how well AI agents handle real small-business work: 200 tasks, sandboxed tools, deterministic grading.
The package that fits
Connector Build
One field service product, one connector, both directory submissions. Several products under one roof is Connector Suite.
Your customers do their real work in your product from inside the assistant they already use. Set scope, set price, quoted in the conversation, and changes to what we built are included.
Straight answers
What teams ask next.
Can a technician use the connector, or only the owner?
Both, if your API supports roles. Each person signs in with their own account, and the tools only return what that account can already see in your product.
Can it take a payment on the spot?
No, by design. Anthropic’s directory does not accept connectors that transfer money. The connector can read what is owed and draft a payment link for the owner to send.
What if our API is key-based today?
I add an OAuth layer in front of it, so each customer signs in to their own account. OpenAI’s submission portal has no API-key flow, so this is needed for ChatGPT anyway.
Sources
I wrote this page for Modern Mustard Seed, and we sell the service it describes. Every fact about Anthropic, OpenAI or another company was read from the page linked here on October 12, 2026.
One next step
Send me your API docs.
Tell me your product and where your API reference lives. I will come back with the jobs your customers would do in Claude and ChatGPT, the tools I would build, and the package that fits. Managed for you, end to end, and the code is yours.
Claude is a product of Anthropic, and ChatGPT is a product of OpenAI. Modern Mustard Seed is an independent studio and is not affiliated with or endorsed by either.