Skip to content
Bkper
Sign in with Google

Bkper MCP

Use the hosted Bkper MCP server for conversational assistant tool calls through existing Bkper permissions.

Bkper MCP is the hosted connector used when ChatGPT, Claude, or another compatible assistant accesses Bkper on the web. The assistant continues using its own models; MCP only provides Bkper tools through your existing account permissions.

This page is a technical orientation. The canonical user setup, endpoint, and current capability reference lives at Bkper MCP.

Use it when

  • You want conversational assistant access to your Bkper books.
  • You are doing quick, read-heavy exploration.
  • You need connector-based access without terminal commands.
  • Local files, shell commands, tests, and scripts are not required.

The hosted endpoint is:

https://mcp.bkper.app/mcp

Follow Bkper MCP for setup instructions because connector screens and capabilities can change.

Public discovery metadata

Agents and connector catalogs can discover the hosted server through these public resources:

These resources describe the existing hosted endpoint. They do not provide a separate sandbox or additional permissions.

Try asking

Good first questions are narrow and reviewable:

  • “List my books and show which one looks like the operating company.”
  • “Show the main accounts and groups in this book.”
  • “Summarize unchecked transactions from last month.”
  • “Find transactions that may need review before reconciliation.”

For any write, give the assistant a standing instruction:

Before making any change in Bkper, explain the exact plan and ask for my confirmation.

Safety model

When you connect Bkper MCP:

  • you authorize access with Bkper OAuth;
  • your existing Bkper permissions still apply;
  • Bkper remains the source of truth for books, transactions, groups, accounts, balances, permissions, lock dates, and audit history;
  • write operations should require an explicit plan and your confirmation before they happen.

Use CLI instead when

If your assistant can run terminal commands, prefer CLI local tools for Bkper work. MCP is usually not the strongest path for work that needs local artifacts:

  • scripts and repeatable reports;
  • shell pipes, jq, CSV transformations, or local files;
  • app development;
  • tests and deterministic build artifacts;
  • long multi-turn work that benefits from project context.

For those workflows, let a desktop assistant install Bkper’s local tools. See Use Bkper with ChatGPT or Claude.