Accounting MCP Accounting MCP

Connect Claude or any MCP client

Every workspace uses the same remote MCP URL:

https://accounting-mcp.com/mcp

Accounting MCP identifies the workspace during OAuth consent and filters tools from that person's live connector access. You do not create a separate URL or client ID for each workspace.

Before connecting

Confirm that:

  1. The person is an active member of the workspace.
  2. The required connector is enabled.
  3. A credential-based connector has an active provider account.
  4. The person is the workspace owner or has a direct or group access grant.

See Connectors, accounts, and access grants for the owner setup.

Connect Claude

For an individual Claude account:

  1. Open Customize > Connectors in Claude.
  2. Select +, then Add custom connector.
  3. Enter https://accounting-mcp.com/mcp as the remote MCP server URL.
  4. Finish adding the connector and select Connect.
  5. In the browser window, sign in to Accounting MCP.
  6. Choose the workspace you want Claude to use.
  7. Review the requested profile:read scope and bound MCP resource, then select Allow.

For a Claude Team or Enterprise organization, an organization owner first adds the URL under Organization settings > Connectors. Each member then opens Customize > Connectors and selects Connect to complete their own Accounting MCP consent.

Claude's current remote connector instructions are available in the Claude Help Center.

After connecting, enable Accounting MCP for a conversation from the + menu and Connectors. Claude will then offer the tools allowed for that workspace member.

What happens during OAuth

An OAuth-capable MCP client completes these steps automatically:

  1. A request without a token receives a WWW-Authenticate challenge that points to Accounting MCP's protected resource metadata.
  2. The client discovers the authorization server and supported endpoints.
  3. The client dynamically registers itself, with no client ID or secret entered by you.
  4. The client opens the Accounting MCP sign-in and workspace consent flow.
  5. Accounting MCP issues an authorization-code token bound to the selected workspace and canonical MCP resource. Dynamically registered clients use PKCE with S256.

The only advertised OAuth scope is profile:read. Connector tools are filtered by workspace enablement, provider account availability, and live member or group grants rather than additional OAuth scopes.

Connect another MCP client

Use a client that supports remote Streamable HTTP MCP servers and OAuth discovery with dynamic client registration. Add the same URL, then follow the browser sign-in and workspace consent flow.

If a client does not support OAuth discovery but can send a static Bearer header, a workspace owner can create an API key under API Keys and configure it as described in the MCP server reference. API keys represent the workspace, not an individual member, so prefer user OAuth when per-person grants matter.

Switch workspaces

Disconnect the Accounting MCP connector in the client and connect it again. Choose the new workspace on the consent screen. Tokens are bound to the workspace selected during consent and cannot be reused for another workspace.

Troubleshooting

  • The connector will not authenticate: remove the client connection and reconnect so it can repeat discovery and consent.
  • A provider tool is missing: confirm the connector is enabled, an active provider account exists, and the member is an owner or has a direct or group grant.
  • A tool stopped appearing: check whether the grant, group membership, connector, provider account, or workspace membership changed.
  • A remote client cannot reach the server: remote clients must be able to access https://accounting-mcp.com/mcp over the public internet.

Use Activity to confirm which MCP requests reached the workspace.