FieldCamp

Connect AI Assistants with MCP | FieldCamp

Connect Claude, ChatGPT, Cursor, and other AI clients to FieldCamp's MCP server, copy secure connection details, and understand current tool limits.

FieldCamp's MCP Servers settings connect supported AI clients directly to FieldCamp. You choose the client you use, then follow its connection instructions with FieldCamp's fixed MCP server URL and your current FieldCamp session token.

This is not a catalogue for installing third-party MCP servers. It does not add external MCP triggers to FieldCamp workflows. If you are building a server-to-server integration instead, use FieldCamp API authentication.

Before you connect

  • Sign in to the FieldCamp account whose data the AI client should access.
  • Install and sign in to the AI client you want to connect.
  • Confirm that your FieldCamp role has access to the records and actions you expect the client to use. The MCP token carries the same permissions as your signed-in user; review roles and permissions before sharing access.

The bearer token shown on this page is your current FieldCamp session token. Treat it like a password. Do not put it in documentation, screenshots, chat messages, or source control.

Open MCP Servers

  1. Open Settings in FieldCamp.
  2. Under Automation, select MCP Servers.
  3. If this is your first connection, select the action to create your first server. Otherwise, select New MCP Server.

MCP Servers is a direct Settings destination. You do not need to enable an MCP add-on under Apps & Integrations first.

Choose an AI client

In New MCP Server, choose the client you want to connect. The current client list includes:

  • Claude Desktop and Claude Code
  • ChatGPT
  • Cursor
  • Python
  • Anthropic API
  • Gemini CLI
  • Kiro
  • Windsurf
  • VS Code

FieldCamp creates a named entry for that client and opens its Connect tab. The entry uses the FieldCamp MCP endpoint at https://mcp.fieldcamp.ai/mcp.

Connect the client

Open the Connect tab

Select the MCP server entry, then open Connect. FieldCamp shows instructions tailored to the client you selected.

Copy the connection details

Use the copy controls beside Server URL and Bearer token. Some clients accept the remote HTTP endpoint directly; others require a local configuration file or bridge command. Follow the instructions shown for that client instead of reusing another client's configuration.

Finish setup in the AI client

Add the configuration where the client instructs you to, then restart or reconnect the client when prompted.

Confirm FieldCamp tools appear

Open the client's MCP or tools panel and confirm that FieldCamp is listed. Run a low-risk read request before allowing the client to make changes.

Name each entry for the client and device it belongs to, such as "Claude Desktop - Office Mac." The name can be edited from the MCP server detail header.

Understand the Apps and History tabs

Each saved MCP server has three tabs:

TabWhat it currently provides
ConnectClient-specific setup instructions, the server URL, and the current bearer token.
AppsThe selected AI client and an Available tools section. Fine-grained tool selection is not currently available, so all FieldCamp tools are exposed to the client within the signed-in user's permissions.
HistoryAn activity area for MCP requests. Activity history is not currently populated, so do not use this tab as an audit log.

The saved MCP server entries are stored in the browser. An entry created on one browser or device might not appear on another. The token itself is taken from your current signed-in FieldCamp session rather than being stored in the saved entry.

Remove a saved entry

Open the server options beside an entry and select Delete server. This removes the saved client entry from that browser. Also remove the FieldCamp MCP configuration from the external AI client so it no longer attempts to connect.

Troubleshooting

The client cannot connect

  • Confirm the server URL is exactly https://mcp.fieldcamp.ai/mcp.
  • Copy a fresh bearer token from Connect after signing in again.
  • Follow the instructions for the selected client; configuration formats and header placement differ between clients.
  • Restart the client if its instructions require a restart after configuration changes.

A tool is missing or an action is denied

Fine-grained tool selection is not available on the Apps tab. If a FieldCamp action is denied, check the permissions of the signed-in user and confirm the target record is available in that FieldCamp account.

The History tab is empty

The current page does not provide a populated request history. Check the external client's own logs when diagnosing a connection or tool call.

Create and Configure AI Agents | FieldCamp

Create a FieldCamp AI agent, choose its model and connections, and configure Manual, Schedule, Event, or API triggers before activation.

Agent Connections | FieldCamp

Connect AI agents to Twilio, Gmail, Google Calendar, QuickBooks, and Stripe so they can make calls, send emails, check schedules, and process payments.

On this page

Before you connectOpen MCP ServersChoose an AI clientConnect the clientUnderstand the Apps and History tabsRemove a saved entryTroubleshootingThe client cannot connectA tool is missing or an action is deniedThe History tab is emptyRelated articles