Read Fieldwire projects, tasks, plans, forms, RFIs and submittals; create and update tasks. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"fieldwire": {
"url": "https://fieldwire.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"fieldwire": {
"type": "http",
"url": "https://fieldwire.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Fieldwire API token and Project data region.
Account Owners and Managers create the token in Fieldwire under Account → API Settings. API access is not on every plan: Fieldwire sells it with the Premier plan or as an add-on to Pro and Business, so ask Fieldwire sales if the section is missing. The token acts as its user. The region is the one your projects live in (US, EU or Canada). Your token is used only to call the Fieldwire API on your behalf; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Fieldwire API token and Project data region. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Tool | Type | What it does |
|---|---|---|
fieldwire_get_account | read | Get account The Fieldwire account this API token belongs to: id, company name and address, enabled modules (submittals, change orders, RFIs, specs, BIM) and the owner. GET /account on the account host. |
fieldwire_list_account_users | read | List account users All users on the account (and users invited to its projects) with name, company, email, account role and the number of projects each is in. User ids are what tasks use for owner and assignees. GET /account/users on the account host. |
fieldwire_list_projects | read | List projects Projects the token's user can access in the region chosen at login: id, name, code, address, time zone, plan and archive state. Filter by name, code, archive state or update time. Use the id in every other tool. GET /api/v3/projects. |
fieldwire_get_project | read | Get project One project by id: name, code, address, time zone, currency, plan, enabled features and owner email. GET /api/v3/projects/{id}. |
fieldwire_list_project_users | read | List project users Users on one project with name, company, job title, email and phone. The integer id is what tasks use for owner_user_id and user_ids. Filter by email, name or company. GET /api/v3/account/projects/{project_id}/users. |
fieldwire_list_tasks | read | List tasks Tasks (punch items, issues) in a project: name, status_id, team_id, location_id, floorplan_id, owner and assignee user ids, priority, dates and cost. Filter by status, team, location, plan, owner, name, tag and dates. Resolve ids with fieldwire_list_task_statuses, _list_teams, _list_locations and _list_project_users. GET /api/v3/projects/{project_id}/tasks. |
fieldwire_get_task | read | Get task One task by id with all its fields. GET /api/v3/projects/{project_id}/tasks/{id}. |
fieldwire_list_task_statuses | read | List task statuses The task statuses of a project (id, name, order, kind open/tracked/verified, default flag). Use the id as status_id on tasks. GET /api/v3/projects/{project_id}/statuses. |
fieldwire_list_teams | read | List teams (task categories) Teams of a project (id, name, handle). The Fieldwire app calls them 'categories' on tasks; tasks carry a team_id. GET /api/v3/projects/{project_id}/teams. |
fieldwire_list_locations | read | List locations Locations of a project (id, name, parent location_id). Tasks carry a location_id. GET /api/v3/projects/{project_id}/locations. |
fieldwire_list_task_check_items | read | List task checklist items Checklist items of all tasks in a project: name, checked flag, state (empty/yes/no/not_applicable) and task_id (match it to the task). GET /api/v3/projects/{project_id}/task_check_items. |
fieldwire_list_floorplans | read | List plans (floorplans) Plans (floorplans) of a project: id, name, description, folder and sheet count. Filter by name, tag or dates. Set with_current_sheet to include each plan's current sheet. GET /api/v3/projects/{project_id}/floorplans. |
fieldwire_list_sheets | read | List sheets Sheets (plan versions) of a project: id, name, file name, version, floorplan_id and file URLs. Filter by plan, folder, name or dates. GET /api/v3/projects/{project_id}/sheets. |
fieldwire_list_attachments | read | List attachments Files, photos, videos and 360 photos attached in a project: id, name, kind, size, capture time and file URLs. Filter by kind. GET /api/v3/projects/{project_id}/attachments. |
fieldwire_list_forms | read | List forms Forms (inspections, daily reports, checklists) of a project: id, name, template, status, owner, dates. Forms need a Business plan. Use fieldwire_get_form_full for the filled-in values. GET /api/v3/projects/{project_id}/forms. |
fieldwire_get_form | read | Get form One form by id (header data only, not the filled-in values). GET /api/v3/projects/{project_id}/forms/{id}. |
fieldwire_get_form_full | read | Get form with all values A form with its sections, inputs and filled-in values. Two steps: call without jid to start the job (Fieldwire answers with a jid); then call again with that jid until the form comes back (answer 'pending' means not ready, retry). GET /api/v3/projects/{project_id}/forms/{id}/full. |
fieldwire_list_form_templates | read | List form templates Form templates of a project: id, name, version, publish state. Use the id to filter forms. GET /api/v3/projects/{project_id}/form_templates. |
fieldwire_list_rfis | read | List RFIs RFIs (requests for information) of a project: number, name, question, answer, status, assignee, due date. Needs the RFI module. Filter by status, assignee, text, overdue or dates. GET /api/v3/projects/{project_id}/rfis. |
fieldwire_list_submittals | read | List submittals Submittals of a project: number, name, status, revision, key dates. Needs the submittals module. Filter by status, assignee, text, overdue or dates. GET /api/v3/projects/{project_id}/submittals. |
fieldwire_create_task | write | Create task WRITE: creates a new task in a project. It is sent once and never retried; if the reply is an error, check fieldwire_list_tasks before creating it again, or you may get a duplicate. owner_user_id and priority are required; creator_user_id defaults to the owner. Find user ids with fieldwire_list_project_users. POST /api/v3/projects/{project_id}/tasks. |
fieldwire_update_task | write | Update task WRITE: changes fields of one task (only the fields you pass; user_ids replaces the whole assignee list; null clears a field that allows it). Use it to set the status, owner, assignees, priority or dates. It does not delete the task. Sent once, never retried. PATCH /api/v3/projects/{project_id}/tasks/{id}. |
fieldwire_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
fieldwire_request_feature | Request a missing feature Tell usefulapi that the user needs something the Fieldwire tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
fieldwire_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Fieldwire tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
fieldwire_cancel_subscription | Cancel the Pro subscription Cancel the caller's Fieldwire Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run fieldwire_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Proper account | $9/mo · $90/yr | Unlimited |
Pro covers this Fieldwire server only. Subscribe with fieldwire_upgrade (it returns a Stripe Checkout link). Cancel any time with fieldwire_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running fieldwire_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Fieldwire. The server calls the Fieldwire API with your own Fieldwire access, so it sees only the data that your account can see.
The login page asks for your Fieldwire API token and Project data region. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Fieldwire API token and Project data region. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Fieldwire API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Fieldwire.
Yes, if you approve it. 2 of the 22 Fieldwire tools can create or change data. The other 20 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Fieldwire server only. Run fieldwire_usage_status to see how many calls you used.
Ask the AI to run fieldwire_upgrade: it returns a Stripe Checkout link. To cancel, run fieldwire_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with fieldwire_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.