fieldpulse_list_job_workflow_statuses — FieldPulse MCP by usefulapi MCP Tool
fieldpulse_list_job_workflow_statuses
(fieldpulse list job workflow statuses) is one of 43 tools on the
FieldPulse MCP by usefulapi
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call fieldpulse_list_job_workflow_statuses from your client
- Claude Code FieldPulse MCP by usefulapi fieldpulse_list_job_workflow_statuses run in your project directory
- Claude Desktop FieldPulse MCP by usefulapi fieldpulse_list_job_workflow_statuses ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor FieldPulse MCP by usefulapi fieldpulse_list_job_workflow_statuses ~/.cursor/mcp.json
- VS Code FieldPulse MCP by usefulapi fieldpulse_list_job_workflow_statuses .vscode/mcp.json
- Zed FieldPulse MCP by usefulapi fieldpulse_list_job_workflow_statuses ~/.config/zed/settings.json
- Windsurf FieldPulse MCP by usefulapi fieldpulse_list_job_workflow_statuses ~/.codeium/windsurf/mcp_config.json
- Cline FieldPulse MCP by usefulapi fieldpulse_list_job_workflow_statuses ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI FieldPulse MCP by usefulapi fieldpulse_list_job_workflow_statuses ~/.gemini/settings.json
- Grok FieldPulse MCP by usefulapi fieldpulse_list_job_workflow_statuses .mcp.json (in your project root)
- ChatGPT FieldPulse MCP by usefulapi fieldpulse_list_job_workflow_statuses Settings → Connectors → Advanced → Developer mode
- Claude.ai FieldPulse MCP by usefulapi fieldpulse_list_job_workflow_statuses Settings → Connectors → Add custom connector
- LangChain FieldPulse MCP by usefulapi fieldpulse_list_job_workflow_statuses pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http fieldpulse https://fieldpulse.usefulapi.io/mcpOther tools on this server
- fieldpulse_list_customers
- fieldpulse_get_customer
- fieldpulse_list_customer_contacts
- fieldpulse_get_customer_contact
- fieldpulse_list_jobs
- fieldpulse_get_job
- fieldpulse_list_job_status_workflows
- fieldpulse_list_estimates
- fieldpulse_get_estimate
- fieldpulse_list_invoices
- fieldpulse_get_invoice
- fieldpulse_list_payments
- fieldpulse_get_payment
- fieldpulse_list_assets
- fieldpulse_get_asset
- fieldpulse_list_asset_categories
- fieldpulse_list_locations
- fieldpulse_get_location
- fieldpulse_list_projects
- fieldpulse_get_project
- fieldpulse_list_contracts
- fieldpulse_get_contract
- fieldpulse_list_items
- fieldpulse_get_item
- fieldpulse_list_purchase_orders
- fieldpulse_get_purchase_order
- fieldpulse_list_vendors
- fieldpulse_get_vendor
- fieldpulse_list_company_profiles
- fieldpulse_list_users
- fieldpulse_list_teams
- fieldpulse_list_tags
- fieldpulse_list_lead_sources
- fieldpulse_list_pipeline_statuses
- fieldpulse_list_custom_fields
- fieldpulse_list_comments
- fieldpulse_list_subtasks
- fieldpulse_list_timesheets
- fieldpulse_create_customer
- fieldpulse_update_customer
- fieldpulse_create_job
- fieldpulse_update_job
This list was read from the server itself, by connecting to it and calling tools/list on 23 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.