Fieldwire MCP connector
The Fieldwire connector brings Fieldwire accounts, users, attachments and files to Claude, ChatGPT, Cursor and the Elaichi Agent, so each person can look things up and update them inside their own Fieldwire access.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Fieldwire to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Fieldwire once
-
Open Connections, choose Add connection, and pick Fieldwire.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Fieldwire API key. One person generates a token in Fieldwire and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Fieldwire MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Fieldwire MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Fieldwire MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Fieldwire to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Fieldwire through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Office admin
Invite a new subcontractor in minutes
Ask for a new crew lead to be invited to the Fieldwire account with the right profile details filled in, instead of clicking through the invite form for each person.
-
Project management
Pull the attachments on a project template
Before kickoff, list every attachment on the project template you are starting from and check nothing is missing or out of date.
-
Field operations
Find the right file without hunting
Give the file reference from a message or a report and get the file details back, without opening Fieldwire and scrolling through folders.
-
IT
Clean up users after a project closes
Update or remove a batch of account users at once when a crew rolls off, so the account only holds the people still on site.
-
Quality control
Restore an attachment removed by mistake
When a photo or document on the account was deleted in error, ask for it to be restored and confirm it is back.
-
Project controls
Keep account data types consistent
Review the custom data types set up on the Fieldwire account, add a missing one, and tidy names so every project records things the same way.
Try asking
- “Invite the new electrical subcontractor to our Fieldwire account”
- “List the attachments on the hospital project template”
- “Show me every user on the Riverside account”
Compare
Elaichi vs Zapier MCP vs Composio for Fieldwire
All three can connect Fieldwire to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Fieldwire tools | Allow or restrict single Fieldwire tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Fieldwire call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
Fieldwire tools for your AI agents
320 tools are ready to call through Elaichi's MCP endpoint the moment you connect Fieldwire, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Showing 241 of 320 Fieldwire tools here. Connect Fieldwire and call search_tools or tools/list over the MCP endpoint for the complete set.
See it in Elaichi
What connecting Fieldwire gets you
6 screens from the product, each doing one job for your Fieldwire account.
The agent
Ask about Fieldwire records in plain language.
Three starter prompts, answers pulled from live Fieldwire accounts, users and attachments.
- accounts
- users
- attachments
- files
Ask Elaichi to work across your apps.
Invite the new electrical subcontractor to our Fieldwire account
List the attachments on the hospital project template
Show me every user on the Riverside account
Also runs in Claude, ChatGPT or Cursor
MCP clients
One Fieldwire endpoint for every MCP client.
Claude, ChatGPT and Cursor reach Fieldwire through one governed endpoint, no SDK, no shared key.
Copy the endpoint
Tool catalog
320 Fieldwire tools, no code to write.
Accounts, users, attachments and files, every method cataloged and ready without a line of code.
- List all Fieldwire accounts
- Fieldwire accounts bulk update
- List all Fieldwire account users
- Get single Fieldwire account user by ID
Toolboxes
Every team gets its own Fieldwire toolbox.
Scope a toolbox to office admins, project managers or the field, each with what they need.
- Office admin
- Project management
- Field operations
- IT
Shared connections
Share one Fieldwire connection, never a credential.
One person connects Fieldwire, teams and members work through it without seeing the API key.
- Commercial
- Residential
- Civil works
- Office admin
Audit log
Every Fieldwire call lands in the audit log.
When, who, what happened, type and resource, for every user invite and attachment change.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule starts Fieldwire work, a person approves.
Fetch new Fieldwire attachments, group them, draft a digest, approve it, post it back.
Fieldwire digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch accounts
Fieldwire
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Fieldwire
Queued
Collections and dashboards
Fieldwire health, computed on a schedule, never requested.
Four metrics, 14 days of attachments created and a breakdown by team, no model involved.
Fieldwire health
Refreshed 4 minutes ago · every 15 minutes · from the accounts collection
Accounts
1,284 ↓ 12%
Users
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Accounts created
Last 14 days
By team
Share of activity
Commercial 34%
Residential 27%
Civil works 21%
Office admin 18%
FAQ
Frequently asked questions
How do I connect Fieldwire to Claude?
Connect Fieldwire in Elaichi by pasting a Fieldwire API key; there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi as yourself, and your Fieldwire accounts, users, attachments and files are ready to ask about.
Does Fieldwire work with ChatGPT and Cursor as well as Claude?
Yes. Fieldwire is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. There is nothing separate to set up for each client.
What can an AI agent actually do with my Fieldwire data?
With Fieldwire connected, you can ask for the users on an account, invite someone new, update a profile, list the attachments on a project template, look up a file by its reference, or restore an attachment that was removed. Short, concrete asks such as "invite Dana to the Riverside account" work better than long sentences.
Does connecting Fieldwire give the AI access to every account and project?
No. Everything the AI does in Fieldwire runs inside the access of the person who signed in, so it sees the accounts, users and attachments that person can already see. Elaichi can narrow that access further with roles and restrictions, and it can never widen it.
Can I stop an agent from deleting or changing things in Fieldwire?
Yes. Restrictions in Elaichi work per action, so you can allow reading Fieldwire users and attachments while blocking deletes or updates. A restricted action is left out of the AI client's tool list entirely, so it cannot be called no matter what the prompt says.
What happens to a Fieldwire connection when someone leaves?
Offboarding a person in Elaichi ends their access to Fieldwire through every client at once. A shared Fieldwire connection keeps working for everyone else on the team. If you want it gone completely, disconnect Fieldwire once in Elaichi and it is removed from Claude, ChatGPT, Cursor and every other client.
Does the Fieldwire MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Fieldwire is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Fieldwire?
Yes. Both let Claude, ChatGPT or Cursor use Fieldwire. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Fieldwire call.
How is Elaichi different from Composio for Fieldwire?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Fieldwire: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Fieldwire in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.