io.usefulapi/fieldwire
up checked
Unclaimed · Unverified
Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.
Publisher-provided title
Fieldwire MCP by usefulapi
Publisher-provided description
Read Fieldwire projects, tasks, plans, forms, RFIs and submittals; create and update tasks.
Summary by lookupd
Lets agents read and update construction project data: tasks, plans, forms, RFIs, submittals, and attachments in Fieldwire.
Install
Claude Code, remote (streamable-http)
claude mcp add --transport http fieldwire https://fieldwire.usefulapi.io/mcp
Codex, remote (streamable-http)
codex mcp add fieldwire --url https://fieldwire.usefulapi.io/mcp
Cursor, remote (streamable-http) → .cursor/mcp.json
{
"mcpServers": {
"fieldwire": {
"url": "https://fieldwire.usefulapi.io/mcp"
}
}
}Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.
Tools (22 tools)
Publisher-provided text
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. GETfieldwire_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 tafieldwire_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 stfieldwire_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 cfieldwire_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 byfieldwire_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}/fieldwire_list_teamsTeams 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_locationsLocations of a project (id, name, parent location_id). Tasks carry a location_id. GET /api/v3/projects/{project_id}/locations.fieldwire_list_task_check_itemsChecklist 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/{profieldwire_list_floorplansPlans (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 currfieldwire_list_sheetsSheets (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/{projfieldwire_list_attachmentsFiles, 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}/fieldwire_list_formsForms (inspections, daily reports, checklists) of a project: id, name, template, status, owner, dates. Forms need a Business plan. Use fieldwire_get_form_full ffieldwire_get_formOne form by id (header data only, not the filled-in values). GET /api/v3/projects/{project_id}/forms/{id}.fieldwire_get_form_fullA 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 jifieldwire_list_form_templatesForm 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_rfisRFIs (requests for information) of a project: number, name, question, answer, status, assignee, due date. Needs the RFI module. Filter by status, assignee, textfieldwire_list_submittalsSubmittals of a project: number, name, status, revision, key dates. Needs the submittals module. Filter by status, assignee, text, overdue or dates. GET /api/v3fieldwire_create_taskWRITE: 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 youfieldwire_update_taskWRITE: 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 s
Details
- Version: 1.24.3
- Transports: streamable-http
- Uptime (7 days): 100%
- Median latency: 455 ms
- First indexed:
- Last seen in registry:
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/fieldwire/
Badge for your README
Shows this live status and links here; updates hourly.
[](https://lookupd.com/servers/io.usefulapi/fieldwire)
- 62071 servers
- Last crawl: 2026-11-11T16:17:25.167Z
- API base:
https://api.lookupd.com - MCP URL:
https://api.lookupd.com/mcp