Field service, connected
Let your AI assistant work with Fieldbase.
Find clients and equipment, prepare work orders, coordinate technicians, and retrieve reports—using the access already defined by your Fieldbase role.
Connect an assistantConnect in a minute
One endpoint works for every assistant below. 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.
https://app.fieldbase.work/api/mcpPick your assistant
- 1Settings → Connectors (turn on 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.
- 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 the connector first.
- 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
- 1Settings → Tools & Integrations → New MCP server
- 2Add a remote (HTTP) server with the endpoint
- 3Reload, then approve the OAuth sign-in
- 1Command Palette → “MCP: Add Server” → HTTP
- 2Paste the endpoint URL
- 3Approve the OAuth sign-in when prompted
- 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; discovery does the rest.
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.
{
"mcpServers": {
"fieldbase": {
"url": "https://app.fieldbase.work/api/mcp"
}
}
}Streamable HTTP · OAuth 2.1 + PKCE · scoped to your Fieldbase role · revoke anytime from Settings