Kobana

MCP servers to build agents on Kobana

Every product has a remote MCP server at mcp.{product}.kobana.com.br, with OAuth 2.1, per-resource scopes and the permissions of whoever authorized it.

See the serversGuide for users
MCP servers to build agents on Kobana

How the MCP servers work

Streamable HTTP, stateless

One JSON-RPC 2.0 message per POST, no session. The URL is the host root, with no path.

OAuth 2.1 with PKCE

The client discovers where to authenticate from the URL and opens the Kobana login screen. There is no client secret.

Personal token, when there's no OAuth

Create a token in the Kobana Account with the product's application and MCP usage, and send it in Authorization: Bearer.

Scope and permissions

The token limits the client by resource and level (read or write). The dashboard permissions of whoever authorized it limit the rest, re-read on every call.

Annotated tools

Each tool declares whether it reads, writes or is destructive. Destructive ones only run after confirmation.

The same barriers as the API

A tool calls the same code as the REST API: enabled account, active subscription, product in the plan and IP allow list.

Servers by product

Paste the product URL into the MCP client. The Banking Gateway also has a sandbox host, with tokens separate from production.

Banking Gateway

289 tools

Production

https://mcp.banking.kobana.com.br

Sandbox

https://mcp.banking.sandbox.kobana.com.br

Operates on the token's account. For a sub-account, send the X-Account-Uid header.

MCP documentation →

Smart Finance

96 tools

Production

https://mcp.finance.kobana.com.br

The workspace is chosen on each call, with finance_workspaces_list and the workspace_id argument.

MCP documentation →

Test the connection

With a token issued for MCP, list the tools it can reach. Swap the host for the product you want to test.

curl https://mcp.banking.kobana.com.br/ \
  -H "Authorization: Bearer $MCP_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "MCP-Protocol-Version: 2025-06-18" \
  -d '{ "jsonrpc": "2.0", "id": 1, "method": "tools/list" }'

If fewer tools come back than you expected, it's the token's scope or the permissions of whoever authorized it. It's not an error.

Connect a client

Any client with Streamable HTTP and OAuth 2.1 connects with just the URL.

Claude Code

Add the server and authenticate with /mcp.

claude mcp add --transport http kobana-banking https://mcp.banking.kobana.com.br

File-configured client

With a personal token, send the authorization header. Treat the file as a secret.

{
  "mcpServers": {
    "kobana-banking": {
      "type": "http",
      "url": "https://mcp.banking.kobana.com.br",
      "headers": {
        "Authorization": "Bearer <token>"
      }
    }
  }
}

Personal token

Kobana Account → Tokens and Access → My Personal Tokens → New Token, with MCP usage. Pick the shortest validity your use allows.

Recommended posture for agents

  • Authorize with the right user: A client authorized by a read-only user only sees read tools, whatever the model does.
  • Ask only for what the agent needs: Select the resources it needs and leave write unchecked for exploratory use.
  • One token per client: Each client gets its own token, valid only for MCP. Revoke it under Authorized Applications without affecting REST integrations.
  • In the Banking Gateway, start in the sandbox: Destructive tools cancel bank slips, pay bills and move real money.
  • Third-party data is not an instruction: Names, descriptions and notes are written by other people. The servers instruct the agent not to follow orders found in those fields.

Just want to use it, not integrate?

We have a guide for connecting your assistant to your Kobana account, with step-by-step instructions for Claude, ChatGPT and Cursor.

See the guide for users

Shall we build your agent?

Tell us what your agent needs to do and we'll help design the integration.

Schedule a call
Schedule