A command line utility for managing Bkper Apps and Bots and running the Model Context Protocol (MCP) server.
The MCP server enables AI assistants and agents to interact with your Bkper books through a standardized protocol.
npm i -g bkper
yarn global add bkper
bun add -g bkper
login- Logs the user in, storing local credentials.logout- Logs out the user by deleting client credentials.mcp start- Start the Bkper MCP (Model Context Protocol) server.apps list- List all apps you have access to.apps create- Create a new App based on./bkperapp.yamlfile.apps update- Update an existing App based on./bkperapp.yamlfile.
bkper loginBkper includes an MCP server that allows AI assistants and other tools to interact with your Bkper books through the Model Context Protocol.
bkper mcp startThe server runs on stdio and provides the following tools:
- list_books - List all books accessible by the authenticated user
- get_book - Get detailed information about a specific book
- get_balances - Get account balances with query filtering
- list_transactions - List transactions with filtering and pagination
- create_transactions - Create transactions in batch
- merge_transactions - Merge duplicate transactions into one
Before using the MCP server:
- Login using
bkper loginto set up authentication
The MCP server uses the same authentication as the CLI, reading credentials from ~/.config/bkper/.bkper-credentials.json.
Add to your configuration file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"bkper": {
"command": "bkper",
"args": ["mcp", "start"]
}
}
}For other MCP-compatible clients, configure them to run:
bkper mcp startThe server communicates via stdio, so any MCP client that supports stdio transport can connect to it.
Once connected, the MCP client can:
- List your Bkper books
- Get detailed book information including group hierarchy
- Get account balances with flexible query filtering
- Search and filter transactions with pagination
- Create transactions in batch
- Merge duplicate transactions
For more information about the Model Context Protocol, visit modelcontextprotocol.io.
BKPER_API_KEY is optional. If not set, uses the Bkper API proxy with a managed API key.
Set it for direct API access with your own quotas and attribution. Follow these steps.
# BASIC APP CONFIGURATION
# The agent id of the App or Bot. It can NOT be changed after the App or Bot is created.
id: my-custom-app
# The readable name of the App or Bot.
name: My Custom App
# The logo url from public host. Best fit 200x200 px. Use https://
logoUrl: https://static.thenounproject.com/png/2318500-200.png
# The logo url to be used when in dark mode
logoUrlDark: https://static.thenounproject.com/png/2318500-200.png
# ACCESS CONTROL (safe to version - uses usernames, not emails)
# Developers who can update the App. Comma or space separated usernames.
# Supports domain wildcards for registered custom domains (e.g., *@bkper.com)
developers: victor, aldo, *@bkper.com
# Users who can use the App while not yet published. Comma or space separated usernames.
# Supports domain wildcards for registered custom domains (e.g., *@acme.com)
users: maria, *@acme.com
# CONTEXT MENU CONFIGURATION
# The menu production url to open in the popup window. See accepted expressions bellow.
menuUrl: https://script.google.com/macros/s/AKfycbxz1Fl1A_KpvAtWLSXtGh1oRaFdWibPweoJfa3yYrFRAAC6gRM/exec?bookId=${book.id}
# The menu development url that will be used while developing.
menuUrlDev: https://script.google.com/a/bkper.com/macros/s/AKfycbwg42np5A-niYBI7Qq2yxOguhcoNgEkqqe0aRLw628/dev?bookId=${book.id}
# The context menu call to action.
menuText: Open My Custom App
menuPopupWidth: 500 # width in pixels. Default to 80% of screen width.
menuPopupHeight: 300 # height in pixels. Default to 90% of screen height.
# BOT EVENTS CONFIGURATION
# The webhook url to be called by Bkper when an event occurs.
webhookUrl: https://us-central1-bkper-tax-trigger.cloudfunctions.net/events
# The events the Bot is capable of processing by the webhook.
# This is optional and, if not specified, no events will be processed.
events:
- "TRANSACTION_POSTED"
- "TRANSACTION_CHECKED"
- "TRANSACTION_UNCHECKED"
- "TRANSACTION_UPDATED"
- "TRANSACTION_DELETED"
- "TRANSACTION_RESTORED"
- "ACCOUNT_CREATED"
- "ACCOUNT_UPDATED"
- "ACCOUNT_DELETED"
- "GROUP_CREATED"
- "GROUP_UPDATED"
- "GROUP_DELETED"
- "FILE_CREATED"
- "BOOK_UPDATED"
# The file patterns the Bot is capable of processing. It accepts wildcards. E.g.
filePatterns:
- "radiusbank*.ofx"
- "-*.qif"
- "*.csv"
# Schema to provide autocompletion on properties editor.
propertiesSchema:
book:
keys:
- "key1"
- "key2"
values:
- "value2"
- "value2"
group:
keys:
- "key1"
- "key2"
values:
- "value2"
- "value2"
account:
keys:
- "key1"
- "key2"
values:
- "value2"
- "value2"
transaction:
keys:
- "key1"
- "key2"
values:
- "value2"
- "value2"${book.id}- the current book id${book.properties.xxxxx}- any property value from the current book${transactions.query}- the current query being executed on transactions list${transactions.ids}- the ids of selected transactions, splitted by comma${account.id}- the current account being filterd${account.properties.xxxxx}- any property value from the current account being filtered${group.id}- the current group being filterd${group.properties.xxxxx}- any property value from the current group being filtered
"menuUrl": "https://app.bkper.com/b/#transactions:bookId=${book.id}"The getOAuthToken returns a Promise that resolves to a valid OAuth token, to be used by the bkper-js library
Example:
import { Bkper } from "bkper-js";
import { getOAuthToken } from "bkper";
Bkper.setConfig({
oauthTokenProvider: async () => getOAuthToken(),
});