The Fieldguide MCP lets you connect Fieldguide to an MCP-compatible AI tool. After you connect it, you can ask your AI tool to retrieve Fieldguide data or complete supported Fieldguide actions without opening Fieldguide for each step.
⠀
MCP stands for Model Context Protocol. It is a standard that lets an AI tool connect to other systems, such as Fieldguide, through a defined set of tools and permissions.
⠀
Before you begin
Before you set up the Fieldguide MCP, make sure you have:
A Fieldguide account.
Access to the Fieldguide data you want to use through the MCP.
Permission to create a Fieldguide API token.
An MCP-compatible AI tool that supports token-based authentication.
⠀
The Fieldguide MCP uses your Fieldguide permissions. If you don't have access to an engagement, request, or action in Fieldguide, your AI tool can't access it through the MCP.
⠀
Generate a Fieldguide API token
The Fieldguide MCP currently uses a Fieldguide API token to connect your AI tool to Fieldguide.
⠀
To create a token, follow the Create an API token steps in Fieldguide API.
⠀
Store the token somewhere secure after you create it. Fieldguide only shows the token once.
⠀
Connect Fieldguide to your AI tool
The setup flow depends on your AI tool. In the tool's MCP connection settings, create a new connection using these values:
Server URL:
https://api.fieldguide.io/mcpAuthentication type: API key or bearer token authentication
Authorization header:
Authorization: Bearer YOUR_TOKEN
⠀
Replace YOUR_TOKEN with the Fieldguide API token you generated.
⠀
Connecting the MCP doesn't move Fieldguide data into your AI tool on its own. Your AI tool sends requests to Fieldguide only when you ask it to use the connection.
⠀
What the Fieldguide MCP supports today
The Fieldguide MCP supports conversational access to common engagement and request workflows. The exact response depends on your Fieldguide permissions and the details you include in your prompt.
⠀
Review engagement status
Ask for a status summary when you want to understand where an engagement stands.
⠀
Example prompts:
What's the current status of the [ENGAGEMENT NAME] engagement?Which requests are open or overdue on [ENGAGEMENT NAME]?Who owns the overdue requests for [ENGAGEMENT NAME]?
⠀
The AI tool can retrieve engagement details and request information, then summarize open requests, overdue requests, owners, and status.
⠀
List outstanding requests
Ask for open or overdue requests when you need a request list across one or more engagements.
⠀
Example prompts:
Show me open requests for [CLIENT NAME].Which requests are overdue across my active engagements?Show me the open requests for [ENGAGEMENT NAME], grouped by owner.
⠀
For broad requests, include a client, engagement, owner, or due-date range in your prompt to help your AI tool return the right results.
⠀
Post follow-up comments on requests
Ask your AI tool to draft and post follow-up comments on Fieldguide requests.
⠀
Example prompts:
Post a follow-up comment on the overdue requests for [CLIENT NAME].Add this comment to [REQUEST NAME]: [COMMENT TEXT].Draft a reminder comment for requests due this week on [ENGAGEMENT NAME].
⠀
For write actions, review the request list and comment text before your AI tool posts anything in Fieldguide. This keeps you in control of what gets added to request activity.
⠀
Create an engagement from a template
Ask your AI tool to create a new engagement from an existing engagement template.
⠀
Example prompts:
Create a new engagement for [COMPANY NAME] from our standard [TEMPLATE NAME] template.Set up a [PERIOD] engagement for [COMPANY NAME] using [TEMPLATE NAME].
⠀
If required details are missing, your AI tool should ask for them before creating the engagement. These details may include the company, template, engagement name, dates, or report issue date.
⠀
What the Fieldguide MCP doesn't support yet
The Fieldguide MCP currently focuses on engagement and request workflows. It doesn't support:
OAuth-based MCP setup.
Insights queries.
Triggering Field Agents, agent runs, or Orchestrator workflows.
Directly modifying documents, forms, or sheets.
⠀
Security and access
The Fieldguide MCP uses your Fieldguide API token to act on your behalf. The token's access is limited by:
Your Fieldguide user permissions.
The scopes assigned to the API token.
Any Fieldguide access restrictions that apply to the underlying engagement, request, or object.
⠀
Keep your API token secure. Don't paste it into prompts or share it in messages. Add it only to your AI tool's MCP connection settings.
⠀
If your AI tool can't access data you expect it to find, check that your Fieldguide account has access to that data and that your API token includes the right scopes.
⠀