fieldwork-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIELDWORK_API_KEY | Yes | Your Fieldwork API key from Settings → Users & Routes → Integration tab. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkA | Verify Fieldwork credentials. Run this first if other tools fail. Calls GET /v3.1/profile. On success returns a small redacted profile summary. |
| how_many_customersA | Answer: "How many customers do I have?", "What's my customer count?" Counts every customer in Fieldwork and breaks down by status. Prefer this over search_customers for total-count questions. |
| how_much_product_was_usedA | Answer: "How much product was used?", "What chemicals did we use this month?" Totals logged material/chemical usage from completed jobs. Args: days: Look back this many days ending today (default 30). Ignored if start_date set. start_date: Optional YYYY-MM-DD range start. end_date: Optional YYYY-MM-DD range end (default today). material_name: Optional filter, e.g. "Alpine" or "Taurus". |
| how_is_business_doingA | Answer: "How is business doing?", "How many jobs did we finish this month?" Plain-English operations snapshot (jobs completed, cancelled, production value). |
| whats_on_the_scheduleB | Answer: "What's on the schedule?", "How many jobs this week?" Work-order overview for a date range (default 7 days). |
| find_customerA | Answer: "Do I have a customer named ___?", "Find customer Smith" Search customers by name or other Fieldwork search text. |
| who_owes_me_moneyA | Answer: "Who owes me money?", "What invoices are unpaid?", "How's my AR?" Totals open invoice balances and lists top customers by amount due. |
| how_much_moneyB | Answer: "How much money did we make?", "What's our revenue this month?" Financial summary snapshot for a date range. |
| who_are_my_techniciansA | Answer: "Who are my technicians?", "Who's on my team?", "What routes do I have?" Lists technicians, office users, and service routes (no secrets). |
| how_are_my_routes_doingC | Answer: "How are my routes doing?", "Which route is busiest?" Jobs (and completions) per service route for a date range. |
| who_did_the_most_jobsA | Answer: "Who did the most jobs?", "Who's my top technician?" Ranks technicians/routes by completed jobs for a date range. |
| what_products_do_we_carryA | Answer: "What products do we carry?", "What chemicals are in our catalog?" Lists materials/products configured in Fieldwork. |
| search_customersA | Search Fieldwork customers. Args: query: Free-text search (name, email, account bits — whatever Fieldwork indexes). page: Page number (default 1). per_page: Page size (default 25; keep modest). start_date: Optional YYYY-MM-DD (or MM/DD/YYYY) lower bound. end_date: Optional YYYY-MM-DD (or MM/DD/YYYY) upper bound. customer_status: Optional status filter. postal_code: Optional postal/ZIP filter. updated_after: Optional updated-after date (YYYY-MM-DD or ISO-8601). |
| get_customerA | Fetch one customer by ID. |
| search_customer_by_phoneA | Find a customer by phone number. |
| list_customer_notesB | List notes on a customer (read-only). |
| list_materialsA | List materials/chemicals in the Fieldwork catalog (name, EPA #, etc.). |
| list_servicesA | List service types configured in Fieldwork. |
| list_service_routesB | List service routes (technician routes). |
| search_work_ordersA | Search work orders / service appointments. Prefer passing start_date and end_date (YYYY-MM-DD) to keep results small. |
| get_work_orderB | Fetch one work order. plain=True uses Fieldwork's show_plain endpoint. |
| get_work_order_service_reportB | Fetch the service report for a work order (often includes treatment details). |
| list_work_order_unit_recordsA | List unit records for a work order. This is the main read path for material usage: usages are nested on unit records in Fieldwork's API (there is no standalone material-usages index). |
| search_invoicesC | Search invoices. |
| get_invoiceA | Fetch one invoice by ID. |
| list_calendar_work_ordersB | List calendar work orders for a date range (YYYY-MM-DD). |
| get_operations_summaryB | Operations summary report for a date range (ISO dates, e.g. 2026-01-01). |
| get_financial_summaryA | Financial summary report for a date range (ISO dates, e.g. 2026-01-01). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| monday_morning_briefing | Owner briefing: business health, who owes money, this week's schedule, product usage, and top technician. Use the matching owner tools. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/daisydaines/fieldwork-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server