Connect FieldEdge to Claude Code
Make Claude create work orders and dispatch technicians in FieldEdge. From the terminal, inside the sessions where you already work.
How do you connect FieldEdge to Claude Code?
Claude Code reaches outside tools through MCP servers. To connect FieldEdge, you add a FieldEdge MCP server: a small hosted service that exposes FieldEdge's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own FieldEdge account. No API keys pasted into config files.
claude mcp add --transport http fieldedge https://your-connector-url/mcpThen run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.
What can Claude Code do in FieldEdge once connected?
Full read-write access lets Claude create and update jobs, schedule and dispatch technicians, edit customer and equipment records, build estimates, and draft invoices, with the outbound and destructive steps held for your approval. The dispatch and follow-up work that meant clicking through screens happens where the job already lives.
- Create a new work order and attach it to the right customer and service location
- Schedule a job and assign it to an available technician on the dispatch board
- Update a customer record, equipment history, or service notes after a visit
- Build an estimate from a job's line items and labor
- Draft an invoice from a completed work order for your review
- Add a follow-up task or reschedule a job when a window changes
One connector, every Claude surface
The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same FieldEdge access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.
Build it yourself, or have it built?
If you live in the terminal, you can absolutely write your own MCP server against the FieldEdge API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when FieldEdge changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build FieldEdge connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.
Frequently asked questions
Does the same FieldEdge connector work in claude.ai and Claude Code?
Do I need to host or maintain anything myself?
Is it safe to give a coding agent write access to FieldEdge?
More on the FieldEdge connector
Tell us what you run. We'll build the connector.
Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.