Fieldbase for AI assistants

Let your AI assistant work with Fieldbase.

Fieldbase runs a secure remote MCP (Model Context Protocol) server. Connect ChatGPT, Claude, Cursor, VS Code, or any MCP-compatible assistant and let it work with your field service operation — using exactly the access your Fieldbase role already grants.

MCP endpoint — works in every assistant belowhttps://app.fieldbase.work/api/mcp

What you can ask it to do

Find a client and list their equipment and service history
Draft or update a work order and check technician assignments
Look up equipment by serial, model, or QR code
Pull a completed work order report or its checklist answers
Check fleet vehicles and who is assigned to them
Look up users and teams (read-only)

Connect in a minute

One endpoint works everywhere. Add it as a remote MCP connector, sign in to Fieldbase once, and approve the access you want. There is no password to share and no API key to copy.

Pick your assistant

ChatGPT

1Settings → Connectors (enable Advanced / Developer mode if asked)
2Create a connector and paste the endpoint
3Sign in to Fieldbase and approve the scopes

Custom connectors need ChatGPT Plus, Pro, Business, Enterprise or Edu.

Claude — web & desktop

1Settings → Connectors → Add custom connector
2Paste the endpoint and save
3Sign in to Fieldbase and approve the scopes

On Team / Enterprise a workspace admin may need to allow it first.

Claude Code — CLI

1claude mcp add --transport http fieldbase https://app.fieldbase.work/api/mcp
2Open Claude Code and run /mcp
3Complete the OAuth sign-in in your browser

Cursor

1Settings → Tools & Integrations → New MCP server
2Add a remote (HTTP) server with the endpoint
3Reload, then approve the OAuth sign-in

VS Code — Copilot agent

1Command Palette → “MCP: Add Server” → HTTP
2Paste the endpoint URL
3Approve the OAuth sign-in when prompted

Any other MCP client

1Add a remote / HTTP MCP server
2Use the endpoint — auth is auto-discovered
3Sign in to Fieldbase and approve scopes

Spec-compliant clients need nothing but the URL.

Secure by design

OAuth sign-in

You sign in on Fieldbase. Your password is never shared with the AI provider.

Scoped to your role

The assistant can only do what your Fieldbase permissions already allow — nothing more.

Revoke anytime

Disconnect any assistant from Fieldbase settings; access is per-token and revocable.

EU data residency

Your data stays in the EU. Multi-tenant isolation keeps each organization separate.

For developers & agents

The server speaks the standard Model Context Protocol over Streamable HTTP with OAuth 2.1 (PKCE) and Dynamic Client Registration. A compliant client only needs the endpoint — it discovers everything else from the well-known metadata.

TransportStreamable HTTP (GET + POST)

AuthorizationOAuth 2.1 + PKCE · Dynamic Client Registration · refresh-token rotation

Protected-resource metadatahttps://app.fieldbase.work/.well-known/oauth-protected-resource

Authorization-server metadatahttps://app.fieldbase.work/.well-known/oauth-authorization-server

Config file (Cursor / VS Code / Claude Code)

{
  "mcpServers": {
    "fieldbase": {
      "url": "https://app.fieldbase.work/api/mcp"
    }
  }
}

Frequently asked questions

What is the Fieldbase MCP server?

It is a remote Model Context Protocol (MCP) server that lets AI assistants like ChatGPT and Claude securely read and act on your Fieldbase field service data — work orders, clients, equipment, reports, fleet, and users — through the same permissions your Fieldbase role already has.

Which AI assistants can connect?

Any MCP-compatible client: ChatGPT (custom connectors), Claude (web, desktop, and Claude Code), Cursor, VS Code (Copilot agent mode), and any other assistant that supports remote MCP servers with OAuth.

Is my data safe?

Yes. You authenticate with OAuth — your Fieldbase password is never shared with the AI provider. The assistant is scoped to your role, access is a revocable token, and data is hosted in the EU with multi-tenant isolation.

Do I need an API key?

No. Connecting uses OAuth sign-in, not a copied key. The assistant registers itself dynamically and you approve access in Fieldbase; you can revoke it at any time from settings.

What can the AI actually do?

It can find clients and their equipment, look up service history, draft and update work orders, check technician and vehicle assignments, and retrieve completed reports and checklist answers — always within your role’s permissions.

How do I connect it to ChatGPT?

In ChatGPT go to Settings → Connectors (enable Advanced / Developer mode if prompted), create a connector, and paste https://app.fieldbase.work/api/mcp. ChatGPT opens Fieldbase to sign in and approve the scopes. Custom connectors require ChatGPT Plus, Pro, Business, Enterprise or Edu.

How do I connect it to Claude?

In Claude go to Settings → Connectors → Add custom connector, paste https://app.fieldbase.work/api/mcp, then sign in to Fieldbase and approve the scopes. In Claude Code, run: claude mcp add --transport http fieldbase https://app.fieldbase.work/api/mcp

What is the MCP endpoint URL?

https://app.fieldbase.work/api/mcp — the same URL works for every MCP client. It uses Streamable HTTP transport with OAuth 2.1 (PKCE) and Dynamic Client Registration.

Ready to connect?

Open Fieldbase and add the connector, or start a free trial first.

Open the connector page Start free trial