Fieldguide MCP server: what it does, scopes, and how to connect Claude

Fieldguide hosts one MCP server. It reads engagements and requests, posts comments and creates engagements, over OAuth (beta) or an API token. Verified 21 Oct 2026.

Official remote MCP · read & write

Hosting: Remote HTTP only, hosted by Fieldguide (https://api.fieldguide.io/mcp). No local server or public repo.
Auth: OAuth (beta) for Claude Enterprise and Microsoft Copilot Studio, enabled by a Fieldguide System Admin; a scoped Fieldguide API token sent as a Bearer header for other MCP clients.
Read / write: Read and write: reads engagement status and requests; writes comments on requests and creates engagements from templates. It can't edit documents, forms or sheets.
Works with: Claude Enterprise and Microsoft Copilot Studio (OAuth, documented); other MCP clients that accept a bearer token.
Plan requirement: A Fieldguide account with the MCP available for your firm. Fieldguide doesn't state a plan tier for the MCP; its API article says the API (and so API tokens) is available to enterprise users. The OAuth path for Claude needs Claude Enterprise.
Last changed: 2026-08-12: Fieldguide MCP announced with Field Financials
Verification: Verified 21 Oct 2026 by theFinanceStack · confidence: high

What can an agent do with Fieldguide through MCP?

It can read engagement status and open or overdue requests, post follow-up comments on requests, and create a new engagement from a template. So far Fieldguide documents nothing beyond those.

Fieldguide documents four workflows. It doesn't publish a tool list or tool count.

Workflow	Reads or writes
Engagement status	Read
Outstanding requests	Read
Comments	Write
New engagements	Write

Before a write

Fieldguide doesn't describe a draft or confirmation step for either write, so treat both as taking effect when the tool runs.
Fieldguide advises reviewing the request list and comment text before the agent posts.
It says the agent should ask for missing details such as company, template, dates or report issue date before it creates an engagement.

Good to know

Nothing in the documented tool set moves money.
The connection acts as you, limited by your Fieldguide permissions, the scopes chosen and any object-level restrictions.

Can

Summarise an engagement's status, its open and overdue requests and their owners
List open or overdue requests across one or more engagements, optionally grouped by owner
Draft and post follow-up comments on requests (Fieldguide describes no draft step, so treat it as posting when the tool runs; needs comments:write)
Create an engagement from an existing engagement template (Fieldguide describes no confirmation step, so treat it as created when the tool runs; needs engagements:write)

Cannot

Run Insights queries, per Fieldguide
Trigger Field Agents, agent runs or Orchestrator workflows, per Fieldguide
Edit documents, forms or sheets directly, per Fieldguide
Connect over OAuth from tools other than Claude Enterprise and Copilot Studio, per Fieldguide

What access does it get?

It gets the scopes chosen when the integration or token is set up, capped by the signed-in user's own Fieldguide permissions. Fieldguide names engagements:read, engagements:write and comments:write as examples.

Where	Scopes and permissions (as documented)	Admin requirement
Fieldguide MCP (remote, OAuth beta: Claude Enterprise, Copilot Studio)	A System Admin selects at least one scope when enabling the integration, or Select all. Fieldguide's docs name engagements:read, comments:write and engagements:write as examples. The server's OAuth metadata lists comments:read, comments:write, companies:read, controls:read, engagements.files:read, engagements:read, engagements:write, files:read, forms:read, insights:read, milestones:read, requests.files:read, requests:read, sheets:read, users:read, webhooks:read and offline_access. Choose read scopes only if you don't want writes.	A Fieldguide System Admin enables the integration under Settings › Integrations › Fieldguide MCP and selects its scopes. Claude: a Claude Enterprise admin adds the custom connector, then each user connects their own Fieldguide login. Copilot Studio: the System Admin enables the Copilot Studio card, and someone with Copilot Studio permission to create and edit agents builds the agent, copies Fieldguide's generated OAuth client ID and secret into it, publishes it and shares it. Treat that client secret like a password. Fieldguide suggests sharing the agent with specific people or security groups instead of the whole organisation.
Fieldguide MCP (remote, API token: other MCP clients)	Scopes are chosen when the token is created under My Profile › Integrations › +Add custom integration. The token is limited to the creating user's permissions and expires in 90 days by default, up to one year, per Fieldguide.	Fieldguide's API article doesn't limit token creation to admins: a user creates a token from their own account, and the token is limited to that account's permissions and the scopes chosen, including write scopes. The MCP article lists permission to create a token as a prerequisite. Fieldguide doesn't document an admin approval step.

How do I connect it?

On Claude Enterprise, a Fieldguide System Admin enables the integration and a Claude admin adds https://api.fieldguide.io/mcp as a custom connector; other clients send a Fieldguide API token as a Bearer header.

Fieldguide System Admin: go to Settings › Integrations › Fieldguide MCP, click Enable on the Claude Enterprise card, select the scopes (read only if you want no writes) and click Enable. Copy the MCP URL from the dialog.
Claude Enterprise admin: open Organization settings › Connectors, click Add, choose Custom, name it (for example Fieldguide MCP) and paste the MCP URL.
Keep Authentication on Sign in now and OAuth client on Use Claude's published identity, then add the connector and test it with your own account.
Each user: Customize › Connectors › Fieldguide › Connect, sign in to Fieldguide in the browser, then enable the connector in a new chat.

Fieldguide documents OAuth for Claude Enterprise only (beta). It doesn't document Claude Pro, Team or Claude Desktop setups. If Fieldguide MCP is missing under Integrations, Fieldguide says to contact its support.

What should a finance team watch for?

Treat the two write tools as changing engagement records the moment they run. Your main controls are the scopes you grant and a review step before anything posts.

Fieldguide doesn't describe a draft or confirmation step for either write, so treat a posted comment and a created engagement as taking effect when the tool runs. Requests are often shared with the client, so treat a posted comment as client-facing. Fieldguide advises reviewing the request list and comment text first; keep tool approval on in your client.
Least privilege: leave comments:write and engagements:write unselected if you only need status and request lists. Fieldguide says read scopes are enough for those.
Request descriptions and comments come back as free text. An injected instruction in one could push the agent to post a comment or create an engagement, so keep human approval on.
API tokens default to 90 days and last up to one year, per Fieldguide. A token in a local client config sits in plain text and is often synced or shared; use the shortest expiry that works.
OAuth is labelled beta in Fieldguide's main MCP article and is limited to Claude Enterprise and Copilot Studio. Fieldguide doesn't publish rate limits.
Fieldguide says connecting doesn't move data into the AI tool on its own; requests go only when you ask. It makes no training statement in these docs, so check Fieldguide's and your AI provider's terms.

How could finance teams and accounting firms use it?

Read access answers status questions about open and overdue requests. Write access lets the agent draft follow-up comments and set up engagements, which a person checks before the agent posts or creates them.

Inside a company

Ask which audit requests assigned to your team are open or overdue and who owns each one.
Summarise where the current audit or review engagement stands before a status call with the firm.
Draft replies to auditor requests as comments for a controller to approve before posting.
Group outstanding requests by owner to plan the week's close and audit work.

At an accounting firm

List overdue requests across active engagements for a client and draft reminder comments for a manager to approve.
Create next period's engagement from the standard template, with the agent asking for dates and report issue date first.
Prepare a partner briefing on engagement status, open requests and owners across a portfolio.
Give staff read-only scopes and keep write scopes for the people who post client-facing comments.

Whatever the use, keep a person approving any comment a client could see and any engagement the agent creates.

Want Fieldguide connected to Claude for your team?

We configure scoped connections and a review step before anything changes your books. Fixed fee.

Book a 30-minute setup call

Change log

Date	Change	Source
2026-10-21	Re-verified: remote URL, OAuth (beta) for Claude Enterprise and Copilot Studio, API token path, four documented workflows; server OAuth metadata lists 16 scopes plus offline_access	help.fieldguide.io/en/articles/16693092-set-up-and-use-the-f
2026-08-12	Fieldguide announces Fieldguide MCP alongside Field Financials	www.cpapracticeadvisor.com/2026/08/13/fieldguide-rolls-out-f
2026-07	Fieldguide MCP starts rolling out to customers, starting with look-ups and routine actions, per CPA Practice Advisor	www.cpapracticeadvisor.com/2026/08/13/fieldguide-rolls-out-f

FAQ

Is this official?

Yes. Fieldguide hosts the server at api.fieldguide.io/mcp and documents it in its own help centre. It isn't listed in Claude's connector directory as of 21 Oct 2026; Claude Enterprise admins add it as a custom connector.

Is it free?

Fieldguide doesn't publish a separate MCP price. You need Fieldguide with the MCP available for your firm; Fieldguide says its API is available to enterprise users. The documented Claude path needs Claude Enterprise.

Does it change data in Fieldguide?

Only if you grant write scopes. With comments:write it can post comments on requests, and with engagements:write it can create engagements from templates. It can't edit documents, forms or sheets, per Fieldguide.

Is my data used to train models?

Fieldguide's MCP docs don't address training. They say data is sent only when you ask the AI tool to use the connection. Check Fieldguide's terms and your AI provider's terms.

Can my accountant use it on my behalf?

Fieldguide doesn't document this. The connection acts as the signed-in user and sees only what that user can access in Fieldguide, so anyone using it needs their own Fieldguide access.

Something wrong or out of date? Tell us and we'll email you when it's fixed.

Sources

Verified by theFinanceStack, 21 Oct 2026. Vendor list on the CFO Software Market Map courtesy of Jason Staats; AI connectivity data by theFinanceStack. Not tax, compliance or financial advice.