Introduction

Claude connects to the FinologeeBKO MCP server as a custom connector, letting you drive the platform through natural-language interaction. Three Claude clients are supported: the Claude Code command-line interface, the Claude Desktop application for Mac and Windows, and claude.ai on the web.

Whichever client you use, Claude acts under your existing FinologeeBKO rights and follows the same signatory-rule approvals that apply elsewhere on the platform. The setup differs only in where you enter the connection details.

Prerequisites

Before connecting, make sure you have:

The MCP server enabled for your tenant. Contact [email protected] to request it.
Your MCP endpoint URL and OAuth client ID. See MCP server for where to find these.
One of the supported Claude clients installed: the Claude Code CLI, the Claude Desktop app, or access to claude.ai.

Connecting with Claude Code

Register the MCP server with the claude mcp add command, using the HTTP transport, your endpoint URL, and your client ID:

claude mcp add -t http finologeebko https://<your-tenant-host>/mcp --client-id <your-client-id>

The flags are:

-t http — uses the streamable HTTP transport. This is required, as the default transport is stdio.
--client-id — your tenant's OAuth client ID.
-s user — optional. Add it to make the server available across all your projects instead of only the current one.

Once the server is registered, start Claude Code and trigger authentication:

Run claude to start a session
Type /mcp
Select the finologeebko server and choose Authenticate
A browser opens at the FinologeeBKO login page. Sign in with your credentials.

Claude Code stores the token and completes the connection. The server status turns to connected.

To remove the server later, run:

claude mcp remove finologeebko

Connecting with Claude Desktop or claude.ai web

In the Claude Desktop app or on claude.ai, add the MCP server as a custom connector:

Open Settings → Connectors → Add custom connector
Enter a Name, for example finologeebko
Set the Remote MCP server URL to your endpoint URL, for example https://<your-tenant-host>/mcp
Open Advanced settings and set the OAuth Client ID to your client ID. Leave the client secret empty.
Click Add, then Connect

A browser opens at the FinologeeBKO login page. Sign in with your credentials. The connector turns to connected and its bko__* tools appear in the tool picker.

Verifying the connection

Confirm the connection is working:

In Claude Code, type /mcp again to list the server's tools. In Claude Desktop or on the web, open the tool picker.
Check that tools appear namespaced bko__<domain>__<verb>, for example:
- bko__cash_account__find_cash_accounts
- bko__counterparty__get_counterparties
- bko__credit_transfer__create
Ask Claude something that uses a tool, such as "list cash accounts", and confirm the tool runs.

Troubleshooting

Symptom	Cause and fix
401 Unauthorized after the connection previously worked	The token has expired. Re-authenticate: in Claude Code, run `/mcp` and select Authenticate again.
Browser redirect or callback is rejected	The redirect URI is not registered for your client. Contact [email protected].
Tools are missing, or a tool call is denied after connecting	Your account lacks the FinologeeBKO rights required for that action. Each tool requires its own permission. Review your permissions with your administrator.

Support

For assistance connecting Claude to the MCP server, contact [email protected].