FieldCamp MCP Server — Connect Your AI Assistant

Any active FieldCamp account. The assistant acts as you — it can see and change exactly what your own role allows, and nothing more. Check roles and permissions if you're unsure what your account can reach.

Claude (Pro, Max, Team or Enterprise for custom connectors), ChatGPT, or any MCP-capable tool such as Cursor, VS Code, Claude Code, Windsurf, Kiro or Gemini CLI.

Claude Desktop reaches remote servers through the mcp-remote bridge, which runs via npx. Install Node.js 18 or newer first. Every other client connects directly and needs nothing extra.

Remote servers are added through Settings → Connectors, not a config file. Requires a Pro, Max, Team or Enterprise plan.

Claude Desktop's config only supports local servers, so we bridge through mcp-remote. Open Settings → Developer → Edit Config and add:

{
  "mcpServers": {
    "fieldcamp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.fieldcamp.ai/mcp",
        "--header",
        "Authorization: Bearer fc_live_YOUR_TOKEN"
      ]
    }
  }
}

Config file location — macOS: ~/Library/Application Support/Claude/claude_desktop_config.json, Windows: %APPDATA%\Claude\claude_desktop_config.json. Quit and reopen Claude Desktop afterwards.

claude mcp add --transport http fieldcamp https://mcp.fieldcamp.ai/mcp \
  --header "Authorization: Bearer fc_live_YOUR_TOKEN"

Add --scope local, project or user to control where the server is registered.

Uses url with a top-level headers object. Add to ~/.cursor/mcp.json (or .cursor/mcp.json for one project):

{
  "mcpServers": {
    "fieldcamp": {
      "url": "https://mcp.fieldcamp.ai/mcp",
      "headers": {
        "Authorization": "Bearer fc_live_YOUR_TOKEN"
      }
    }
  }
}

Different shape: the top-level key is servers, and headers go inside requestInit. Add to .vscode/mcp.json:

{
  "servers": {
    "fieldcamp": {
      "url": "https://mcp.fieldcamp.ai/mcp",
      "requestInit": {
        "headers": {
          "Authorization": "Bearer fc_live_YOUR_TOKEN"
        }
      }
    }
  }
}

To keep the token out of git, use VS Code's ${input:…} prompt instead of hard-coding it.

Uses serverUrl, not url:

{
  "mcpServers": {
    "fieldcamp": {
      "serverUrl": "https://mcp.fieldcamp.ai/mcp",
      "headers": {
        "Authorization": "Bearer fc_live_YOUR_TOKEN"
      }
    }
  }
}

Uses httpUrl. Either run:

gemini mcp add --transport http fieldcamp https://mcp.fieldcamp.ai/mcp \
  -H "Authorization: Bearer fc_live_YOUR_TOKEN"

or add to settings.json:

{
  "mcpServers": {
    "fieldcamp": {
      "httpUrl": "https://mcp.fieldcamp.ai/mcp",
      "headers": {
        "Authorization": "Bearer fc_live_YOUR_TOKEN"
      },
      "timeout": 30000
    }
  }
}

Any MCP-capable client works: point it at https://mcp.fieldcamp.ai/mcp over Streamable HTTP and send Authorization: Bearer fc_live_…. For clients that only speak local (stdio) servers, bridge with npx -y mcp-remote https://mcp.fieldcamp.ai/mcp --header "Authorization: Bearer fc_live_YOUR_TOKEN".

FieldCamp's Settings → Automation → MCP Servers page generates ready-made snippets for the Anthropic API and Python (fastmcp) too.

Read — list and filter clients, open a client, see their jobs, documents, products and payment history. Write — create a client. Destructive — update or delete a client.

Read — list and open jobs and visits, visit stats, next job number. Write — create jobs and visits. Destructive — update or delete a job or visit.

Read — list tasks, open a task, list the tasks on a job or against a client. Write — create a task. Destructive — update or delete a task.

Read — list and open service requests. Write — create a request, convert a request into an estimate. Destructive — update or delete a request.

Read — list and open estimates and invoices, payment history, next document number. Write — create documents, email a document to a client, record a payment received. Destructive — update or delete documents and payments.

FieldCamp records that a payment was received (cash, cheque, transfer). The connector never charges a card or moves money.

Read — browse products and services, categories, inventory, warehouses, vendors, tax rates, purchase orders. Write — create products, warehouses, vendors, tax rates, purchase orders. Destructive — update, delete or transfer inventory.

Read — calendar events and activity, availability, schedule conflicts, team members, dispatch suggestions. Write — create calendar events. Destructive — update or delete calendar events.

Read only — business analytics, company info, account data model, record change history, units of measurement, cross-record search and fetch-by-id.

The only FieldCamp MCP endpoint is https://mcp.fieldcamp.ai/mcp. Never enter a look-alike URL — a spoofed server could capture your token.

A fc_live_… token grants the same access you have. Keep it out of git and screenshots. Revoke any token you've exposed under Settings → Company → API Tokens.

Write and destructive tools are annotated so your assistant prompts before running them. Keep those confirmations on, especially for deletes.

Content inside your records (a client note, a request description) is data, not instructions. Review any action an assistant proposes after reading external content before approving it.

The token was rejected, so the client fell back to trying OAuth. Check the token is current (regenerate under Settings → Company → API Tokens), that it's sent as Authorization: Bearer fc_live_…, and that you used the right config key for your client (url vs serverUrl vs httpUrl). For Claude Desktop, clear the bridge's cached auth with rm -rf ~/.mcp-auth and restart.

Your grant is missing that scope. Disconnect and reconnect, approving the extra areas (for example jobs:write to create jobs). With an API token, confirm it was generated from the MCP Servers page so it carries the full MCP scope set.

OAuth access tokens refresh automatically — approve the reconnect prompt if you see one. API tokens don't expire but can be revoked; generate a new one if it was.

Any MCP client that supports remote Streamable HTTP works — use the URL and Bearer header. If it only supports local servers, bridge with mcp-remote as shown in the Claude Desktop section.

Restart the client completely (quit, don't just close the window). For Claude Desktop the first launch also downloads mcp-remote via npx, which can take a few seconds.