Read FieldPulse customers, jobs, estimates, invoices, assets and projects; create and update jobs. Hosted by usefulapi — connect from Claude, ChatGPT, 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": {
"fieldpulse": {
"url": "https://fieldpulse.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"fieldpulse": {
"type": "http",
"url": "https://fieldpulse.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
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 FieldPulse API token.
FieldPulse issues API tokens through support: email [email protected] (or use the chat in the app) to have a token registered and activated for your account. The token is sent only to the FieldPulse 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 FieldPulse API token. 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.
Turn on the FieldPulse connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
fieldpulse_list_customers | read | List customers List or search customers (name, email, phone, address, status, assigned user). GET /customers. |
fieldpulse_get_customer | read | Get customer One customer by id. GET /customers/{id}. |
fieldpulse_list_customer_contacts | read | List customer contacts The contacts (people) of one customer. GET /customers/{customerId}/customer-contact. |
fieldpulse_get_customer_contact | read | Get customer contact One contact of a customer. GET /customers/{customerId}/customer-contact/{contactId}. |
fieldpulse_list_jobs | read | List jobs List or search jobs (type, status, customer, schedule, assignments), optionally within a created-at range or by custom status ids. GET /jobs. |
fieldpulse_get_job | read | Get job One job by id, optionally with its custom field values. GET /jobs/{id}. |
fieldpulse_list_job_status_workflows | read | List job status workflows The job status workflows (use their ids with fieldpulse_list_job_workflow_statuses and when setting a custom job status). GET /jobs/status-workflows. |
fieldpulse_list_job_workflow_statuses | read | List job workflow statuses The custom job statuses of all workflows, with their ids (for filtering jobs or setting a status). GET /jobs/status-workflow-statuses. |
fieldpulse_list_estimates | read | List estimates List or search estimates (customer, status, totals, line items). GET /estimates. |
fieldpulse_get_estimate | read | Get estimate One estimate by id. GET /estimates/{id}. |
fieldpulse_list_invoices | read | List invoices List or search invoices (customer, status, totals, due dates). GET /invoices. |
fieldpulse_get_invoice | read | Get invoice One invoice by id. GET /invoices/{id}. |
fieldpulse_list_payments | read | List payments List or search payments (amount, method, date, invoice). GET /payments. |
fieldpulse_get_payment | read | Get payment One payment by id. GET /payments/{id}. |
fieldpulse_list_assets | read | List assets List or search customer assets (equipment) by install status. GET /assets. |
fieldpulse_get_asset | read | Get asset One asset by id. GET /assets/{id}. |
fieldpulse_list_asset_categories | read | List asset categories List asset categories. GET /assets-category. |
fieldpulse_list_locations | read | List locations List locations (service addresses) of a customer or a job. GET /locations. |
fieldpulse_get_location | read | Get location One location by id. GET /locations/{id}. |
fieldpulse_list_projects | read | List projects List or search projects (status, completion). GET /projects. |
fieldpulse_get_project | read | Get project One project by id. GET /projects/{id}. |
fieldpulse_list_contracts | read | List contracts List contracts (maintenance agreements). GET /contracts. |
fieldpulse_get_contract | read | Get contract One contract by id. GET /contracts/{id}. |
fieldpulse_list_items | read | List items List the invoice item catalog (products and services with prices). GET /items. |
fieldpulse_get_item | read | Get item One invoice item by id. GET /items/{id}. |
fieldpulse_list_purchase_orders | read | List purchase orders List purchase orders. GET /purchase-orders. |
fieldpulse_get_purchase_order | read | Get purchase order One purchase order by id. GET /purchase-orders/{id}. |
fieldpulse_list_vendors | read | List vendors List vendors (suppliers). GET /vendors. |
fieldpulse_get_vendor | read | Get vendor One vendor by id. GET /vendors/{id}. |
fieldpulse_list_company_profiles | read | List company profiles The company profile(s) of this FieldPulse account (name, address, contact details, settings). GET /company-profile. |
fieldpulse_list_users | read | List users List the account's users (team members) with ids for assignments. GET /users. |
fieldpulse_list_teams | read | List teams List the account's teams. GET /teams. |
fieldpulse_list_tags | read | List tags List tags for customers or jobs. GET /tags. |
fieldpulse_list_lead_sources | read | List lead sources List customer lead sources. GET /lead-source. |
fieldpulse_list_pipeline_statuses | read | List pipeline statuses List customer pipeline statuses. GET /pipeline-status. |
fieldpulse_list_custom_fields | read | List custom fields List custom field definitions, optionally for one object type. GET /custom-fields. |
fieldpulse_list_comments | read | List comments List comments on a record (customer, job, project, subtasks, invoice). GET /comments. |
fieldpulse_list_subtasks | read | List subtasks List subtasks (job checklist items) by status or assigned user. GET /subtasks. |
fieldpulse_list_timesheets | read | List timesheets List timesheet entries (clock in/out), optionally for one user or a time window. GET /timesheets. |
fieldpulse_create_customer | write | Create customer WRITE: create a customer (lead or account). Give first_name and/or last_name, or a unique display_name. Creates a new record every call; check fieldpulse_list_customers first to avoid duplicates. POST /customers. |
fieldpulse_update_customer | write | Update customer WRITE: change fields of one customer (only the fields you pass). If FieldPulse asks for a name, include first_name/last_name or display_name. PUT /customers/{customerId}. |
fieldpulse_create_job | write | Create job WRITE: create a job for an existing customer. Needs customer_id, job_type and the numeric billing value FieldPulse requires; set a status (1-6) or a custom status_id + status_workflow_id. Creates a new job every call. POST /jobs. |
fieldpulse_update_job | write | Update job WRITE: change a job: status, schedule, notes, assignments, location. FieldPulse requires customer_id, job_type and billing on every update, so this reads the job first and keeps those (and its current status) unless you pass new values. The read and the write are two requests; FieldPulse offers no version check. PUT /jobs/{jobId}. |
fieldpulse_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. | |
fieldpulse_request_feature | Request a missing feature Tell usefulapi that the user needs something the FieldPulse 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. | |
fieldpulse_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED FieldPulse tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a short link to open in your browser (it opens Stripe Checkout); after payment your account upgrades automatically. Does not count against the meter. | |
fieldpulse_cancel_subscription | Cancel the Pro subscription Cancel the caller's FieldPulse 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 fieldpulse_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper API key | $9/mo · $90/yr | Unlimited |
Pro covers this FieldPulse server only. Subscribe with fieldpulse_upgrade (it returns a Stripe Checkout link). Cancel any time with fieldpulse_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running fieldpulse_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 FieldPulse. The server calls the FieldPulse API with your own FieldPulse access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your FieldPulse API token. See Before you connect for where to find it.
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 FieldPulse API token. 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 FieldPulse 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 FieldPulse.
Yes, if you approve it. 4 of the 43 FieldPulse tools can create or change data. The other 39 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this FieldPulse server only. Run fieldpulse_usage_status to see how many calls you used.
Ask the AI to run fieldpulse_upgrade: it returns a Stripe Checkout link. To cancel, run fieldpulse_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 fieldpulse_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, ChatGPT, Codex, 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.