MCP Connections & Custom Triggers | FieldCamp

Q: Can I write my own MCP server?

Yes. Any server that implements the Model Context Protocol can be registered as a custom server in FieldCamp.

Install MCP connections, register custom MCP servers, and inspect per-connection triggers so your AI agents and workflows can act across the tools you already use.

The MCP add-on extends FieldCamp's AI agents and workflows with external tools through the Model Context Protocol. With MCP connections and custom triggers you can browse the connector library, install pre-built apps, register your own MCP servers, and review the triggers and actions each connection exposes — without writing code.

This guide walks field-service owners and dispatchers through enabling the add-on, installing a connector, adding a custom MCP server, and using the triggers it unlocks inside agents and workflows.

What is MCP in FieldCamp?

Model Context Protocol (MCP) is an open standard for letting AI assistants talk to outside tools — Slack, HubSpot, internal databases, or anything else that exposes an MCP server. Inside FieldCamp, MCP acts as a universal bridge so your AI agents and workflows can read data, send messages, or fire actions in those external tools.

Each MCP connection ships with one or more triggers (events that can start a workflow) and actions (things an agent can do). FieldCamp inspects the server, lists what's available, and lets you wire it into automations the same way you would a built-in integration.

MCP is part of the FieldCamp add-ons catalogue. See FieldCamp Add-Ons — All Features Explained for billing details and how add-ons activate on your plan.

Enable the MCP add-on

The MCP catalogue is unlocked through your plan's add-ons section.

Open add-ons

Go to Settings > Plan & Billing > Add-Ons, or open the add-ons overview from the sidebar.

Activate MCP Connections

Find MCP Connections in the list and switch it on. Owners and admins can toggle this — see Roles & Permissions if the option is greyed out.

Confirm billing

Review the add-on's pricing and confirm. The MCP tab appears under Apps & Integrations within a minute of activation.

If you do not see the Plan & Billing area, you may not have the right role. Check the billing and subscription guide for which roles can manage add-ons.

Browse the connector catalogue

Once the add-on is on, open Settings > Apps & Integrations > MCP Connections. You'll see two tabs:

Catalogue — pre-built connectors maintained by FieldCamp (CRMs, accounting tools, communication apps, internal data stores).
Custom Servers — MCP endpoints you register yourself.

Use the search bar or category filters to find a connector. Each card shows:

A short description of what the server does.
The number of triggers and actions it exposes.
Whether it is OAuth-based or token-based.
A link to the underlying integration if there is also a native FieldCamp app (see Apps & Integrations).

Install a connector from the catalogue

Open the connector card

Click any connector in the catalogue to open its detail page. You'll see the full trigger and action list, scopes the server will request, and any setup notes.

Authenticate

Click Connect. For OAuth connectors, you'll be redirected to sign in to the third-party app and approve the requested scopes. For token-based connectors, paste the API key or access token when prompted.

Name the connection

Give the connection a friendly name (for example, "Sales HubSpot" or "Ops Slack"). Useful when you connect to multiple accounts of the same tool.

Save

Save the connection. It now appears in the Installed list and is available to agents and workflows. See Agent Connections for how installed connections become available to individual agents.

Register a custom MCP server

If your business runs a private MCP server — for an internal database, a niche industry app, or a homegrown tool — you can register it directly.

Open Custom Servers

Inside MCP Connections, switch to the Custom Servers tab and click + Add MCP Server.

Enter the endpoint

Provide the server's URL (must support the standard MCP transport, typically HTTPS with SSE or HTTP streaming) and a display name.

Provide authentication

Choose the auth method your server requires — bearer token, basic auth, or OAuth client credentials — and paste the values. Credentials are encrypted at rest.

Inspect the server

FieldCamp connects to the server and lists every tool, trigger, and resource it advertises. Review the list to confirm it matches what you expect.

Enable and save

Toggle the triggers and actions you want available to agents and workflows. Save to make the connection live.

Only register MCP servers you trust. A custom server has the same access your agent has — the same permissions, the same data. Limit which fields are exposed and rotate credentials regularly.

Inspect triggers per connection

Every connection has a Triggers view that shows what events it can fire into FieldCamp. Click the connection from the Installed list, then open the Triggers tab to see:

Trigger name (for example, "New deal created", "Message received in #ops").
Sample payload — useful when designing a workflow.
Last fired timestamp and recent run log.
An Enable/Disable toggle per trigger so you can turn off the ones you do not need.

Disabled triggers stay registered but don't run, which keeps your audit log clean and rules predictable.

Use MCP connections in agents

MCP connections plug into agents the same way built-in tools do.

Open an agent under AI Agents. If you are new to agents, start with the Building and Managing AI Agents guide and the Creating & Configuring Agents walkthrough.
Scroll to the Connections section and click + Add Connection.
Pick the MCP connection you installed. Choose which of its actions the agent is allowed to call.
Save the agent. It will now use those MCP actions when the conversation calls for them. The Command Centre AI Chat can also call these actions when you wire them into an agent it routes to.

Give the agent clear instructions about when to use each MCP action. A line like "Use the HubSpot MCP only to look up the deal stage" is enough to keep behaviour predictable.

Use MCP triggers in workflows

Custom triggers let your workflow builder start runs from outside events. You can also drop agents directly into a flow — see Agents in Workflows for that pattern.

Create or edit a workflow.
In the trigger picker, choose MCP Trigger and pick the connection.
Select the specific event (for example, "New row in Airtable orders table").
Map the payload fields to FieldCamp records — client, job, visit, or a custom object.
Add the actions the workflow should run when the trigger fires.

Common patterns:

A CRM "deal won" event creates a job and assigns a technician.
A Slack message in a watched channel opens a new request in the sales pipeline.
A custom inventory MCP triggers a workflow to deduct parts after a visit closes.

Manage and revoke connections

You can audit and clean up MCP connections at any time.

Edit to rename, change which triggers are enabled, or update credentials.
Pause to keep the configuration but stop all triggers and agent actions temporarily.
Revoke to remove the connection entirely. Any agents or workflows referencing it will surface a warning so you can repoint them.

The audit log under Settings > Security records every connect, edit, and revoke event with the user who performed it.

Best practices

Keep credentials scoped to the minimum permissions the server needs.
Name connections by team and account, not by tool — "Ops Slack" beats "Slack" when you have several workspaces.
Disable triggers you are not using; it reduces noise and makes the workflow trigger picker easier to scan.
For shared servers, register one connection and reuse it across agents instead of one per agent.
Test new triggers in a draft workflow before turning them loose on live jobs. The workflow examples and pre-built templates are good starting points.

Troubleshooting

The connector won't authenticate

Double-check that the OAuth scopes you approved match what the server requested. For token-based servers, regenerate the token in the source app and paste the fresh value. If the source app uses IP allowlisting, add FieldCamp's outbound IPs (listed on the connection setup page).

A trigger isn't firing

Open the connection's Triggers tab and check the trigger's last fired timestamp and recent log. If the source app hasn't sent an event, the trigger won't show recent activity. Confirm the source app has the right webhook or polling configuration.

My custom server isn't listed

Make sure the server endpoint is reachable from the public internet and returns a valid MCP handshake. Internal-only servers must be exposed through a tunnel, gateway, or VPN that FieldCamp can reach.

An agent can't see an MCP action

Confirm the action is enabled on the connection AND added to the agent's allowed actions list. Both must be on for the agent to call it.

FAQs

Do MCP connections work in every plan? The MCP add-on requires activation on your plan. Review availability under add-ons.

Can I connect the same tool twice (for example, two HubSpot accounts)? Yes. Install the connector, authenticate the first account, then click + Add Connection again on the same card to add the second.

Are credentials safe? Yes. OAuth tokens and API keys are encrypted at rest and never shown back in clear text after they're saved.

Will MCP triggers run for archived clients or paused workflows? No. Archived clients and paused workflows skip MCP-triggered runs, just like any other workflow.

Can I write my own MCP server? Yes — any server that implements the Model Context Protocol can be registered as a custom server.