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

CLI vs MCP

Choose the right AI workspace for Bkper work: local CLI tools whenever possible, hosted MCP when local tools are not available.

Use the CLI/local-tool path whenever possible. Use MCP when local tools are not possible or when a hosted assistant is the right workspace.

This is not about one agent brand. The same rule applies to Bkper CLI Agent, Claude Code, Codex, Cursor, OpenCode, Pi, OpenClaw, Hermes Agent, and other agents that can operate local tools and files.

Choose by workspace

Use CLI/local tools when the work needs files, scripts, tests, shell commands, CSVs, jq, project context, or repeatable financial artifacts.

Use MCP/hosted assistants when you want connector-based access in ChatGPT, Claude, or another hosted client and local tool access is not available or not needed.

If both are possible, start with CLI/local tools.

Why CLI/local tools are stronger by default

Durable context

Local workspaces preserve files, scripts, fixtures, exports, tests, and intermediate artifacts. An agent can create a report script today, improve it tomorrow, and leave a reproducible trail in your project.

A hosted chat can remember a conversation, but it usually does not own the same durable working directory.

Pipes and deterministic tools

CLI output can be filtered, transformed, reviewed, and fed into other deterministic tools:

bkper transaction list -b <bookId> -q 'on:2026-06' --format json \
  | jq '.items[] | {date, description, amount}'

That matters in finance. Raw LLM output should not be the final word on balances, statements, reconciliations, or taxes. Local tools make it easier to produce auditable artifacts.

Agentic capability

Local agents can:

  • read and write project files;
  • run bkper commands;
  • call APIs through scripts;
  • run tests and formatters;
  • iterate on failures;
  • leave checked-in code or reports behind.

Computer-use and “claw” agents such as OpenClaw, Hermes Agent, and similar tools are especially strong with the CLI path because they can operate local tools and files.

Common choices

Prefer CLI/local tools for:

  • building a script, report, or app;
  • using project files, tests, fixtures, or AGENTS.md;
  • running shell pipes, jq, or CSV workflows;
  • producing deterministic financial artifacts;
  • drafting or mutating Bkper data when review and confirmation are required.

Prefer MCP for:

  • quick questions in ChatGPT or Claude;
  • read-heavy exploration;
  • listing books, accounts, groups, transactions, or balances from a hosted assistant;
  • workflows where the assistant has no local files, shell, or CLI access.

Both can be useful for quick book-structure exploration. For mutations, prefer CLI/local tools if possible and always require explicit confirmation.

MCP in local coding tools

Some coding tools can use MCP as an additional connector. That can be useful, but it is not the same as local CLI plus shell plus project context.

If your agent can run local commands, prefer the Bkper CLI for Bkper operations and use MCP as a supplement only when it fits the workflow.

  1. If you can use a terminal workspace, install and authenticate the Bkper CLI.
  2. Use Bkper CLI Agent or your preferred local coding agent with the Bkper CLI skill/plugin.
  3. Use Bkper MCP Server when you need hosted assistant access or cannot use local tools.
  4. For any mutation, require an explicit plan and confirmation before data changes.