Skip to content
Bkper
app.header.homeapp.header.docsapp.header.apps
Open Bkper

Bkper MCP Server

Use the hosted Bkper MCP server to connect ChatGPT, Claude, and other MCP clients to Bkper through existing permissions.

Bkper MCP is the hosted Model Context Protocol server for Bkper. It lets ChatGPT, Claude, and other MCP clients work with your Bkper books through your existing Bkper account permissions.

This page is a high-level orientation. The canonical setup, endpoint, and current capability reference lives at Bkper MCP.

Use it when

  • You want to ask a hosted assistant about your Bkper books.
  • You are doing quick, read-heavy exploration.
  • You need connector-based access without a local terminal setup.
  • 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.

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

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, use local CLI tools whenever possible. See CLI vs MCP.