Fieldwire MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

Fieldwire MCP by usefulapi is answering right now. Last checked 14 min ago. It exposes 22 tools. Last commit 13 Oct 2026.

Read Fieldwire projects, tasks, plans, forms, RFIs and submittals; create and update tasks.

Uptime history 4 days of history

4 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

99 ms

Response time

average over 24h

Stars

last commit 13 Oct 2026

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 13 October 2026. No other catalogue keeps this.

13 Oct a tool changed version

Nothing serious here today

Today is the operative word: we check Fieldwire MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add fieldwire --transport http https://fieldwire.usefulapi.io/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "fieldwire": {
      "url": "https://fieldwire.usefulapi.io/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.fieldwire]
url = "https://fieldwire.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "fieldwire": {
      "url": "https://fieldwire.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "fieldwire": {
      "url": "https://fieldwire.usefulapi.io/mcp"
    }
  }
}

Available tools 22

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

fieldwire

fieldwire_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_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_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

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_get_project

One project by id: name, code, address, time zone, currency, plan, enabled features and owner email. GET /api/v3/projects/{id}.

fieldwire_get_task

One task by id with all its fields. GET /api/v3/projects/{project_id}/tasks/{id}.

fieldwire_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_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_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_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_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_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_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_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_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_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_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_list_task_check_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_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_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_list_teams

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_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}.

Endpoints

URL	Transport	State	Latency	Checked
https://fieldwire.usefulapi.io/mcp	streamable-http	answering	86 ms	14 min ago

Alternatives to Fieldwire MCP by usefulapi

same job, measured the same way

Propstack MCP by usefulapi

by usefulapi

Read Propstack contacts, properties, projects, deals, tasks, events; create and update CRM records.

18 tools answering

Connecteam MCP by usefulapi

by usefulapi

Read Connecteam users, shifts, time clock, jobs, time off, tasks and forms; create shifts and tasks.

19 tools answering

Linear MCP by usefulapi

by usefulapi

Search, read and create Linear issues, projects, teams and cycles.

8 tools answering

Fillout MCP by usefulapi

by usefulapi

Read Fillout forms and submissions, export responses, and create submissions and webhooks.

9 tools answering

Wufoo MCP by usefulapi

by usefulapi

Read forms, fields, entries, reports and comments by field title, and submit entries.

18 tools answering

Harvest MCP by usefulapi

by usefulapi

Read time entries, projects, clients, tasks and invoices; log and update tracked time.

20 tools answering

Reclaim.ai MCP by usefulapi

by usefulapi

Read tasks, habits, events and scheduling links; create and update Reclaim tasks and habits.

15 tools answering

Tick MCP by usefulapi

by usefulapi

Read Tick clients, projects, tasks, users and time entries; log and edit time entries.

14 tools answering

Fieldwire MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Fieldwire MCP by usefulapi do?

It exposes 22 tools, read directly from the server on our last check. Among them: fieldwire_create_task, fieldwire_get_account, fieldwire_get_form, fieldwire_get_form_full, fieldwire_get_project, fieldwire_get_task and 16 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Fieldwire MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 99 ms. The bar chart above shows every period we have measured.

How do I connect Fieldwire MCP by usefulapi?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Fieldwire MCP by usefulapi need an API key?

No. Fieldwire MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 22 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Fieldwire MCP by usefulapi?

It answers our handshake in 99 ms on average, which is faster than 85% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Fieldwire MCP by usefulapi open source?

Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.