Access and manage field service jobs, customers, invoices, estimates and assets from FieldPulse.
Connects to FieldPulse field service management software. Read customers, jobs, estimates, invoices, assets, projects, contracts and timesheets. Create and update jobs. Designed for small service businesses managing field operations.
Try asking Muse: "Show me all open jobs assigned to my team this week and their customer contact information."
Source: Found in the official MCP Registry (io.usefulapi/fieldpulse) · First listed October 29, 2026
Each bar is one check, every 15 minutes. Green means it answered. Last checked 2 h ago.
What Muse can see: It does not ask you to sign in, so it cannot see your accounts. It only sees what Muse sends it from your request.
Before it acts: Read what Muse plans to do before you approve it, and remove the app from Muse when you stop using it.
musedirectory.ai is not part of Meta. More about how Muse handles your information
Not in Muse's Connectors list yet, but Muse can still use it. Copy the request below and paste it into Muse. Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
https://fieldpulse.usefulapi.io/mcpNot in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
FieldPulse MCP is a remote MCP server, so any assistant that can add a custom connector by link can use it. Same link, same tools.
In ChatGPT, open Settings, then Connectors (called Apps & Connectors on some accounts).
Under Advanced settings, switch on Developer mode. That is what lets you add a connector by link.
Choose Create, give it a name, paste the link as the MCP server URL, and save. If it needs a sign-in, ChatGPT asks for it here.
Start a chat, open the tools menu, pick the connector, and ask. ChatGPT asks before it runs a tool the first time.
Custom connectors need a paid ChatGPT plan, and on Team, Enterprise and Edu accounts only an admin can add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in ChatGPT
In Claude, open Settings, then Connectors.
Choose Add custom connector, give it a name, and paste the link.
If it needs a sign-in, Claude sends you to it. Then turn the connector on in a chat from the tools menu and ask.
Custom connectors are available on paid Claude plans; on Team and Enterprise accounts an admin may need to add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in Claude
https://fieldpulse.usefulapi.io/mcpResponse time at the last check: 354ms. Worked in n/a of checks over 30 days.
Screened, no issues found
Screening looks for known threats and hidden instructions at the time of the check, and runs again weekly and whenever the tool list changes. It cannot see the server's code, so only connect what you need and review what Muse asks to do. How screening works.
fieldpulse_list_customersList or search customers (name, email, phone, address, status, assigned user). GET /customers.fieldpulse_get_customerOne customer by id. GET /customers/{id}.fieldpulse_list_customer_contactsThe contacts (people) of one customer. GET /customers/{customerId}/customer-contact.fieldpulse_get_customer_contactOne contact of a customer. GET /customers/{customerId}/customer-contact/{contactId}.fieldpulse_list_jobsList or search jobs (type, status, customer, schedule, assignments), optionally within a created-at range or by custom status ids. GET /jobs.fieldpulse_get_jobOne job by id, optionally with its custom field values. GET /jobs/{id}.fieldpulse_list_job_status_workflowsThe 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_statusesThe custom job statuses of all workflows, with their ids (for filtering jobs or setting a status). GET /jobs/status-workflow-statuses.fieldpulse_list_estimatesList or search estimates (customer, status, totals, line items). GET /estimates.fieldpulse_get_estimateOne estimate by id. GET /estimates/{id}.fieldpulse_list_invoicesList or search invoices (customer, status, totals, due dates). GET /invoices.fieldpulse_get_invoiceOne invoice by id. GET /invoices/{id}.fieldpulse_list_paymentsList or search payments (amount, method, date, invoice). GET /payments.fieldpulse_get_paymentOne payment by id. GET /payments/{id}.fieldpulse_list_assetsList or search customer assets (equipment) by install status. GET /assets.fieldpulse_get_assetOne asset by id. GET /assets/{id}.fieldpulse_list_asset_categoriesList asset categories. GET /assets-category.fieldpulse_list_locationsList locations (service addresses) of a customer or a job. GET /locations.fieldpulse_get_locationOne location by id. GET /locations/{id}.fieldpulse_list_projectsList or search projects (status, completion). GET /projects.fieldpulse_get_projectOne project by id. GET /projects/{id}.fieldpulse_list_contractsList contracts (maintenance agreements). GET /contracts.fieldpulse_get_contractOne contract by id. GET /contracts/{id}.fieldpulse_list_itemsList the invoice item catalog (products and services with prices). GET /items.fieldpulse_get_itemOne invoice item by id. GET /items/{id}.fieldpulse_list_purchase_ordersList purchase orders. GET /purchase-orders.fieldpulse_get_purchase_orderOne purchase order by id. GET /purchase-orders/{id}.fieldpulse_list_vendorsList vendors (suppliers). GET /vendors.fieldpulse_get_vendorOne vendor by id. GET /vendors/{id}.fieldpulse_list_company_profilesThe company profile(s) of this FieldPulse account (name, address, contact details, settings). GET /company-profile.fieldpulse_list_usersList the account's users (team members) with ids for assignments. GET /users.fieldpulse_list_teamsList the account's teams. GET /teams.fieldpulse_list_tagsList tags for customers or jobs. GET /tags.fieldpulse_list_lead_sourcesList customer lead sources. GET /lead-source.fieldpulse_list_pipeline_statusesList customer pipeline statuses. GET /pipeline-status.fieldpulse_list_custom_fieldsList custom field definitions, optionally for one object type. GET /custom-fields.fieldpulse_list_commentsList comments on a record (customer, job, project, subtasks, invoice). GET /comments.fieldpulse_list_subtasksList subtasks (job checklist items) by status or assigned user. GET /subtasks.fieldpulse_list_timesheetsList timesheet entries (clock in/out), optionally for one user or a time window. GET /timesheets.fieldpulse_create_customerWRITE: 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.https://fieldpulse.usefulapi.io/mcpNot in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use FieldPulse MCP to help me. It is a free service with an MCP server at https://fieldpulse.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
At the last check (October 29, 2026, 21:21 UTC) the endpoint was working, answering in 354ms. It is checked every 15 minutes.
It was screened on October 29, 2026 with the result "screened, no issues found". Screening checks the domain against threat feeds and reads the tools for hidden instructions and requests for passwords or card numbers. It cannot see the server's code, so grant only the access you need.
It exposes 40 tools, including fieldpulse_list_customers, fieldpulse_get_customer, fieldpulse_list_customer_contacts, fieldpulse_get_customer_contact. For example, you could ask Muse: "Show me all open jobs assigned to my team this week and their customer contact information."
This listing was added from public sources (Found in the official MCP Registry (io.usefulapi/fieldpulse)). If you build FieldPulse MCP, claim it to correct the details and get your badge.
Paste this on your site or README. It always shows the latest check.
<a href="https://musedirectory.ai/connector/fieldpulse-mcp"><img src="https://musedirectory.ai/badge/fieldpulse-mcp.svg" alt="FieldPulse MCP on musedirectory.ai" width="236" height="40"></a>