The Fieldified MCP Server connects your Fieldified account to MCP-compatible AI assistants. You can use it with tools such as ChatGPT, Claude, Gemini, Codex, and other clients that support custom MCP servers.
Quick answer
Open Settings > Team Organization > MCP Server, generate your personal MCP Server URL, copy it into your AI client’s custom MCP connector, and choose No authentication when prompted.
Treat the MCP Server URL like a password. The URL is shown in full only when it is generated or rotated.
What is MCP?
MCP stands for Model Context Protocol. It lets AI applications connect to external systems through controlled tools.
For Fieldified, MCP lets an AI assistant search, read, create, and update approved Fieldified records without copying information manually between apps.
What the Fieldified MCP Server can help with
Depending on your role permissions, an AI assistant can help you:
- Search Fieldified records across clients, properties, work, schedules, invoices, notes, and reports.
- Read client, property, request, quote, job, visit, invoice, checklist, expense, and timesheet details.
- Create or update supported clients, properties, requests, quotes, jobs, invoices, notes, tasks, events, timesheets, and expenses.
- Complete assigned visits or assessments after required checklists are finished.
- Record invoice payments, approve timesheets, update reimbursements, and review payroll confirmation data.
- Run supported Fieldified reports.
See Fieldified MCP Server Actions and Fields for the full action reference.
Availability
MCP Server Integration is available for Enterprise accounts.
Each user creates their own MCP connection. A user’s MCP access depends on:
- Account plan.
- Account-level MCP switch.
- The user’s role having MCP Server Integration enabled.
- The user’s existing entity permissions for clients, requests, quotes, jobs, invoices, reports, schedule, notes, timesheets, expenses, and other modules.
Enabling MCP does not give a user extra Fieldified permissions. If a user cannot view or edit a record in Fieldified, MCP tools should also block that action.
Security notes
Your MCP Server URL is a credential.
Do not share it publicly, paste it into tickets, store it in shared documents, or send it in chat. Rotate it if it may have been exposed.
Fieldified stores only a hashed token. The raw URL is shown only after you generate or rotate it.
Every MCP tool call is audited with the user, client name, tool name, status, and timestamp.
Enable MCP access for a role
Administrators can open Settings > Team Organization > Roles & Permissions.
To allow a role to use MCP:
- Open the role.
- Enable MCP Server Integration.
- Review the role’s module permissions.
- Save the role.
- Ask the user to generate their own MCP URL from MCP Server settings.
Review client, pricing, invoice, payment, report, timesheet, expense, and schedule permissions carefully before giving MCP access.
Generate your MCP Server URL
- Log in to Fieldified.
- Open Settings.
- Select Team Organization.
- Open MCP Server.
- Select Generate URL.
- Copy the MCP Server URL.
- Store it only in the MCP client you trust.
The full URL is shown only once. If you close the page or lose the URL, use Rotate URL to create a new one.
Rotate or disable MCP
Use Rotate URL when:
- The URL may have been shared.
- A device or AI client is no longer trusted.
- A team member wants to reset their connection.
- You need a new copyable URL.
Use the connection toggle to disable your personal MCP URL.
Administrators can also use the account-level MCP switch to stop MCP access for every user in the account.
Connect to an AI client
In your AI assistant:
- Open connector, integration, or MCP settings.
- Add a custom MCP server.
- Name it Fieldified.
- Paste the Fieldified MCP Server URL.
- Choose No authentication if the client asks for an authentication method.
- Save and test the connection.
The generated MCP URL itself is the credential.
Review audit logs
Open MCP Server settings to review audit logs.
Use filters to check:
- Tool name.
- Status.
- User.
- Client.
- Time.
Review audit logs after rotating a URL, changing a user’s role, testing a new AI client, or investigating unexpected activity.
Common use cases
Daily operations brief
Ask the assistant to show assigned work, visits, assessments, tasks, and schedule events for the day.
Client or property summary
Ask for a client or property summary with recent requests, quotes, jobs, invoices, notes, and outstanding work.
Quote or job preparation
Ask the assistant to review a request or quote and draft next steps, checklist items, or a job setup outline.
Financial follow-up
Ask for unpaid invoices, payment status, deposit history, or invoice receivables summary where your role allows it.
Field completion
Ask the assistant to read a visit, review required checklist status, and complete the visit when requirements are met.
Best practices
- Use specific record names, slugs, dates, client names, and property addresses.
- Ask for short tables, briefs, checklists, or drafts.
- Review every tool request before approving it in your AI client.
- Be extra careful with write actions such as creating invoices, recording payments, approving timesheets, or completing visits.
- Rotate the URL if it may have been exposed.
- Disable MCP when it is not in use.
Troubleshooting
I cannot generate a URL
Confirm your account is on the Enterprise plan and your role has MCP Server Integration enabled.
The AI client cannot connect
Check that the copied URL is complete, your MCP connection is enabled, the account-level MCP switch is enabled, and the URL has not expired or been rotated.
The client asks for authentication
Choose No authentication. The Fieldified MCP Server URL already contains the credential.
A tool says my role does not have access
Your Fieldified role may not include the required module permission. Ask an administrator to review your role in Roles & Permissions.
The URL is masked
Masked URLs cannot be copied as credentials. Rotate the URL to reveal a new full URL.