Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Fieldwire to Claude Code

Make Claude create, assign, and update jobsite tasks in Fieldwire. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Fieldwire to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Fieldwire, you add a Fieldwire MCP server: a small hosted service that exposes Fieldwire'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 Fieldwire account. No API keys pasted into config files.

claude mcp add --transport http fieldwire https://your-connector-url/mcp

Then 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 Fieldwire once connected?

Full read-write Fieldwire access lets Claude create and assign tasks to a plan location, update task status and priority, post messages or photos to a task, add punch-list items, and draft form entries once you approve. The field coordination that used to mean re-keying between the jobsite and the office happens inside the project where the work already lives.

  • Create a task on a project and pin it to a plan location
  • Assign a task to a team member and set its priority and due date
  • Update task status as work moves from open to completed
  • Post a message, comment, or photo to an existing task
  • Add a punch-list item tied to a plan and trade
  • Draft a form or inspection entry for your review before it is submitted

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 Fieldwire 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 Fieldwire API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Fieldwire 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 Fieldwire 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 Fieldwire connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Fieldwire account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Fieldwire's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Fieldwire?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Fieldwire account it signs in with. Revoking access is one click in Fieldwire.

More on the Fieldwire connector

Fieldwire connector for claude.aiMyCase + Claude CodePracticePanther + Claude CodeFilevine + Claude Code

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.

Build my connectorTalk to us