Fieldwire MCP by usefulapi
by FastDrop
Read Fieldwire projects, tasks, plans, forms, RFIs and submittals; create and update tasks.
Read Fieldwire projects, tasks, plans, forms, RFIs and submittals; create and update tasks. Official MCP Registry: io.usefulapi/fieldwire@1.0.0. Remote endpoint: https://fieldwire.usefulapi.io/mcp
Problem it solves
Discoverable MCP server listed in the official MCP Registry.
How it's different
Remote MCP endpoint ingested from the official registry and probed by FastDrop.
Ingested from the official MCP Registry
FastDrop pulled this entry from the official MCP Registry as io.usefulapi/fieldwire and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed
and the description is not theirs.
If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.
Claim this listingTools this endpoint exposes
Read directly from the endpoint on 12 Oct 2026. Not supplied by the maker.
fieldwire_get_accountThe 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_usersAll 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 /ac
fieldwire_list_projectsProjects 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
fieldwire_get_projectOne project by id: name, code, address, time zone, currency, plan, enabled features and owner email. GET /api/v3/projects/{id}.
fieldwire_list_project_usersUsers 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/{pr
fieldwire_list_tasksTasks (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, nam
fieldwire_get_taskOne task by id with all its fields. GET /api/v3/projects/{project_id}/tasks/{id}.
fieldwire_list_task_statusesThe 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.
Is this tool yours?
Claim this listing and we’ll verify ownership before handing it over.
Sign in to claim this listingSimilar launches
Matched on shared tags and the tools their MCP servers actually expose.
Shares tags: MCP server
Shares tags: MCP server
Shares tags: MCP server
Shares tags: MCP server
Shares tags: MCP server
Shares tags: MCP server
Reviews
Sign in to leave a review.
No reviews yet.
Comments
Sign in to join the discussion.
No comments yet - start the discussion.