Connect an AI client
AI clients connect to FieldTask through its MCP server. You add FieldTask's MCP URL to the client, an organization owner or admin signs in and approves access, and the client can then use FieldTask's tools within the permissions you chose.
Before you start
- You need to be an owner or admin of the FieldTask organization.
- FieldTask must have enabled API and MCP access for the organization. If it hasn't, choose Request API access in Settings → API connections.
- Your client must support remote MCP servers over HTTP with OAuth sign-in. There's no API key to paste.
Your organization's MCP URL is shown in Settings → API connections (Copy MCP URL). The examples below use the placeholder https://api.fieldtask.example/mcp.
Connect from FieldTask
The easiest way is to start from FieldTask:
- Open Settings → API connections.
- Under AI assistants, choose your client, for example Connect Claude.
- Follow the steps shown. FieldTask opens the client with the URL filled in where the client supports it.
- When the FieldTask sign-in page opens, sign in, choose the organization and the access to give, and choose Allow access.
- Ask the client something like "What jobs are scheduled for tomorrow?" to check the connection.
The connection then appears under Active connections, where you can change its access or revoke it.
Client-specific steps
These steps match FieldTask's connect screens for the contract this site documents. Client interfaces change often, and compatibility with each client hasn't yet been verified for this release.
| Client | Steps |
|---|---|
| Claude | Choose Add to Claude in FieldTask. Claude opens its custom connector dialog with FieldTask filled in. Choose Add, then Connect, and approve on the FieldTask page. |
| ChatGPT | Choose Copy URL and open ChatGPT. In ChatGPT's connector settings, turn on Developer Mode, choose Add connector, name it FieldTask, paste the URL, then Connect and approve on the FieldTask page. |
| Cursor | Choose Add to Cursor, confirm the install, then approve on the FieldTask page. |
| VS Code | Choose Install in VS Code, confirm the install and start the server, then sign in and approve on the FieldTask page. |
| Other MCP apps | Find the option to add a remote MCP server or connector, paste the MCP URL, then sign in and approve when asked. No client ID or key is needed. |
Command-line clients
For Claude Code:
claude mcp add --transport http fieldtask https://api.fieldtask.example/mcp
For Codex:
codex mcp add fieldtask --url https://api.fieldtask.example/mcp
Use your organization's MCP URL instead of the placeholder. The client opens the FieldTask sign-in page the first time it uses the server.
Manual registration
Most clients register themselves automatically when they connect. If yours needs a client ID registered in advance, use For developers → Register MCP client manually in Settings → API connections and enter the client's callback URL. FieldTask creates a public OAuth client that signs in with PKCE (there's no client secret) and shows its client ID and the MCP URL. Approval still happens on the FieldTask sign-in page.
What the client can do
The tools a client sees depend on the permissions you approved and the features FieldTask has enabled. Ask the client to list its FieldTask tools, or see the tool reference.
To change access later, see Permissions. Added permissions wait for approval: the person who connected the client must reconnect and approve, then refresh the client's tools.
Disconnect
- An owner or admin can Revoke the connection in Settings → API connections. It stops working immediately; records it created stay in FieldTask.
- Reconnect signs the client out so it can connect again.