Accounting MCP Accounting MCP

Connectors, accounts, and access grants

Accounting MCP separates the capability you enable, the provider credentials it uses, and the people allowed to use it. Workspace owners manage all three from Connectors under Gateway.

Available today

  • FreeAgent uses OAuth and provides five read tools for bank accounts, bank transactions, invoices, bills, and profit and loss.
  • ElevenLabs uses an API key and provides outbound Conversational AI calls and transcript downloads.
  • Accounting MCP Diagnostics is built in and provides a gateway status tool without a provider account.

The MCP server reference is the source of truth for the complete public tool list.

The three parts

Part What it controls
Connector The provider capability and tools enabled for this workspace
Account The provider credentials and connector-specific configuration used for calls
Access grant The member or group allowed to use read, write, or destructive tools, optionally routed to a specific account

Active owners always have all three tiers for enabled connectors. Viewers and editors need a direct grant or membership in a granted group.

1. Enable or connect a connector

  1. Open Connectors under Gateway.
  2. Choose FreeAgent or ElevenLabs.
  3. For FreeAgent, select Connect FreeAgent and approve the OAuth request. Accounting MCP enables FreeAgent only after the company is connected and verified.
  4. For ElevenLabs, select Enable connector before adding an account.

Enabling makes the connector eligible for this workspace. Credential-based tools are not ready for user OAuth sessions until the connector also has an active account. Canceling or failing FreeAgent authorization leaves a disabled connector disabled.

2. Add a provider account

On the connector page, select Add account. For ElevenLabs, enter:

  • Account name, such as Production or Client A
  • API key
  • Agent ID
  • Phone Number ID

Select Save account, then Verify to check the stored configuration against the provider.

FreeAgent uses a different account flow: selecting Connect FreeAgent authorizes the company and enables the connector after a successful return. See Connect FreeAgent for the dedicated-user recommendation, reconnect flow, sandbox configuration, and upstream revocation steps.

Provider credentials are encrypted at rest. ElevenLabs API keys are accepted once and never displayed again; FreeAgent OAuth tokens remain server-side. Accounting MCP resolves the credential when a permitted tool runs, and MCP clients never receive it.

Provider scopes are an extra ceiling

Use a provider's read-only or operation-scoped credential when it is available. Provider scope can restrict a credential further, but it can never widen the Accounting MCP tiers granted to a person or group. FreeAgent exposes no OAuth scopes, so Accounting MCP's five registered read tools and live gateway filtering form the effective operation boundary.

You can add more than one account to the same connector. Disconnecting an account stops new calls from using it immediately but preserves its historical activity references.

3. Create groups when access is shared

Open Groups under Admin to create a workspace-local group and add active members. Use groups when several people should receive the same connector access, such as an operations team or client team.

Group membership and group grants are independent. Add the members first, then grant the connector to the group from the connector page.

4. Grant connector access

  1. Return to the connector page.
  2. Under Access, select Grant access.
  3. Choose a member or group.
  4. If more than one active provider account exists, choose Route calls to.
  5. Leave Write and Destructive off for read-only access, or enable either tier explicitly.
  6. Select Grant access.

Every active grant includes Read. Write and Destructive are independent, so a grant may allow destructive tools without granting ordinary write tools. New grants and reactivated grants default to read-only.

When grants overlap, the effective permissions are the union of the direct grant and every active group grant. For example, a direct read-only grant plus one group write grant and another group destructive grant confers all three tiers.

Account routing considers only grants that confer the tool's tier. A qualifying direct grant takes precedence, followed by each qualifying active group grant, then the workspace's oldest active account. A direct read-only grant therefore does not mask a group account authorized for write.

Review or revoke access

The Access list shows each member or group, permission tiers, who granted access, and any account routing. Owners can change Write and Destructive independently. Read is fixed while the grant is active; select Revoke access to remove read and deactivate the entire grant. Nonowners see tier badges without controls.

Access is evaluated whenever an MCP client lists or calls tools. Existing user tokens do not keep stale permissions.

What a member sees

A user-authorized MCP session sees:

  • Built-in gateway tools
  • Tools from enabled connectors whose tier is included in the member's direct/group union, or all tiers when the member is an active owner
  • Credential-based connector tools only when an active provider account is available

Workspace API keys represent the workspace rather than an individual member. For compatibility, they receive all three tiers for enabled connectors without a member grant, but credential-based calls still need an active account. Workspace-token tier configuration must be revisited before Accounting MCP registers its first destructive tool.

Next steps