Fieldified MCP Server Actions and Fields

This article explains the main actions available through the Fieldified MCP Server and how AI assistants can search, read, create, or update Fieldified data through controlled tools.

Quick answer

Fieldified MCP supports account-scoped search, read, and non-destructive write actions for core Fieldified workflows. Available actions depend on your Enterprise plan, account settings, role permissions, and module feature flags.

General rules

• MCP tools are scoped to one Fieldified account and one Fieldified user.
• MCP tools do not accept account_id from the AI client.
• List actions are paginated.
• Search and read actions do not modify records.
• Write actions reuse Fieldified’s existing workflow handlers where possible.
• Delete, archive, void, refund, and raw SQL actions are not exposed.
• Raw file uploads, image uploads, and signature uploads are not supported through MCP.
• Pricing fields can be hidden when the user’s role does not allow pricing access.
• Chemical treatment tools require chemical tracking to be enabled for the account.
• Bid tools require bidding to be enabled for the account.

Search and context actions

Example prompt:

Show my Fieldified MCP account context, then search for open jobs and unpaid invoices related to Green Valley.

Supported entity actions

Identifiers and common fields

Use stable identifiers when possible.

Common identifiers include:

• Client slug.
• Request slug.
• Quote slug.
• Job slug.
• Invoice slug.
• Property ID.
• Contact ID.
• Visit ID.
• Checklist instance ID.
• Assessment ID.
• Expense ID.
• Timesheet ID.

The AI client should not ask you to provide an account ID. Fieldified derives account context from your MCP connection.

Clients, properties, and contacts

Client and property tools can:

• List and read clients.
• Create and update client identity and primary communication details.
• List, read, create, and update properties.
• List, create, and update client contacts.
• List property contacts.

Common fields include client name, company name, primary email, primary phone, tags, property name, address, billing address, tax rate, and contact communication details.

Example prompt:

Find clients matching “Green Valley”. Show their properties, primary contact details, open jobs, and any unpaid invoices.

Requests and assessments

Request tools can:

• Create requests from a client and optional property.
• Update request basics, overview, and products.
• Read request details, products, assessment details, and recent notes.
• Update request assessment details.
• Mark request assessments complete when allowed.

Common fields include title, client slug, property ID, service details, request products, assessment schedule, team members, and notes.

Example prompt:

Read request req_123 and summarize the client, property, requested service, assessment schedule, products, and next recommended action.

Quotes and bids

Quote tools can:

• Create quotes from a client, property, and optional request.
• Update quote introduction, line items, discounts, tax, client message, disclaimer, rate opportunity, and salesperson.
• Update allowed quote statuses.
• Read quote details, totals, line items, salespeople, and recent notes.

Bid tools can list and read bids when bidding is enabled.

Example prompt:

Review quote q_123. Show line items, total, deposit/payment breakdown, client message, and any missing information before sending.

Jobs and visits

Job tools can:

• Create one-off or recurring jobs.
• Update job products.
• Update sales information.
• List and read jobs with visits, invoices, line items, salespeople, and recent notes.

Visit tools can:

• List visits.
• Read visit details.
• Show assigned work for today.
• Complete a visit when the user has permission and required checklists are complete.

Example prompt:

Show my assigned work today. Include visit times, client names, property addresses, pending checklist counts, and any incomplete assessments.

Invoices and payments

Invoice tools can:

• Create invoices.
• Update invoice details, products, totals, messages, visibility, and status.
• List deposits.
• Record offline invoice payments with an idempotency key.
• List and read invoices.

Common fields include subject, client slug, property ID, job slug, line items, due date, payment terms, discounts, tax, totals, client message, invoice visibility, deposit amount, and payment method.

Example prompt:

Find unpaid invoices due this week. Show client, invoice number, due date, total, balance, and recommended follow-up.

Notes and scheduling

Note tools can create, update, and list text notes for supported records.

Schedule task and event tools can create, update, list, and read tasks or events. Schedule permissions determine whether a user can work only with their own schedule or broader team schedules.

Example prompts:

Add a note to job job_123: Customer asked us to call before arriving and prefers morning visits.

Create a task for tomorrow to follow up on quote q_123 with the assigned salesperson.

Timesheets, expenses, payroll, and reimbursements

Timesheet tools can:

• Create and update timesheets.
• List timesheets.
• Show pending approvals.
• Approve one or more timesheets where permitted.
• Read payroll confirmation data.

Expense tools can:

• Create and update expenses.
• List expenses.
• Update reimbursement status.

Example prompt:

Show pending timesheets for this week grouped by employee, then identify any entries missing job links or notes.

Checklists and field completion

Checklist tools can:

• List checklist templates.
• List checklist instances attached to a target.
• Read checklist instance answers.
• Save supported answers.
• Complete an instance when required questions are answered.

MCP does not support image or signature answers. Use the Fieldified app for those responses.

Example prompt:

Read checklist instance 456 and tell me which required questions still need answers before the visit can be completed.

Chemical treatments

Chemical treatment tools can create, list, and read chemical treatment records when chemical tracking is enabled.

Common fields include client, property, job, applicator, treatment date, weather notes, target pest or area, chemicals, quantities, units, and application details.

Example prompt:

List chemical treatments for the last 30 days for property 123 and summarize products used, applicators, and treatment notes.

Reports

Report tools can list available reports and run supported reports. Report permissions still apply.

Supported report families can include visits, job performance, requests, quote conversion, invoice receivables, products and services, timesheet labor, expenses and reimbursements, checklist compliance, and client re-engagement.

Example prompt:

Run the invoice receivables report for this month and summarize overdue balances by client.

Troubleshooting

The assistant says a record was not found

Check that you used the correct slug or ID and that your role has access to that record.

A write action is blocked

Your role may not include create or edit permission for that module, or the action may require a related permission such as pricing, schedule, payment, timesheet approval, or reports.

The assistant asks for many approvals

Ask for a summary or table first, then approve only the specific write action you want.

The assistant cannot upload an image or signature

Use Fieldified web or mobile app for raw files, photos, and signatures. MCP supports text and structured fields only.

Security best practices

• Treat the MCP URL like a password.
• Rotate the URL if exposed.
• Disable MCP when not in use.
• Review every write action before approving it.
• Verify AI-generated notes, messages, totals, schedule dates, and payment details.
• Use least-privilege roles for MCP users.
• Review MCP audit logs after testing or changing permissions.

Related articles

• Fieldified MCP Server
• Set Up Roles and Access
• Add and Manage Team Members