Check connection
Verify the configured Boolance session against the authenticated API without returning user details.
get_connection_status
BOOLANCE × MCPYour books.
Your books.
In your agent’s context.
One connection. Seven useful tools.
Real financial context, right where you build.
Your coding agentQuestions in your workflow
↔Boolance MCPSeven validated tools
↔Your organizationAuthenticated API records
A SMALL, USEFUL TOOLBOXLess tab switching.
Less tab switching.
More context.
Search transactions. Inspect an account. Pull a report.
Every tool uses your authenticated organization’s API.
Reporting dates
Read the workspace's default reporting dates and timezone.
get_date_contextConnected accounts
Read accounts and balances visible to the authenticated organization.
list_accountsBookkeeping categories
Read the organization's categories and linked chart of accounts.
list_categoriesSearch transactions
Search and paginate transactions by date, text, account, category, and review status. Dates default to the workspace reporting range.
list_transactionsTransaction detail
Read one transaction and its supporting context by ID within the authenticated organization.
get_transactionFinancial reports
Read a profit and loss, balance sheet, cash flow, or trial balance report for explicit dates. Includes currency, report basis, and readiness warnings.
get_reportYOUR EDITOR. YOUR CONFIG.A few steps.
A few steps.
A lot more context.
Choose your client and generate its configuration.
Credentials stay in your terminal and private session file.
LOCAL STDIO CONNECTION
Client documentation Connect Codex.
Requires Node.js 22+, pnpm, a local checkout of Boolance, and a running Boolance API with an existing account. Paths stay in this browser tab.
Use absolute paths. Store the session file outside your repository. Enter file paths only, never a password or token.
01
Install the bridge
Run from your Boolance repository root.
pnpm --filter @boolance/mcp install02
Sign in locally
The helper prompts for your password in your terminal and saves a private session file. Replace the API origin for your deployment.
Add your paths above to generate the sign-in command.03Merge into
~/.codex/config.toml// Add your two local paths to generate a configuration.
// No credentials are entered on this page.Preserve your other servers. Restart your client, enable Boolance, and approve tool access when prompted. If a desktop app cannot find Node, replace node with its absolute executable path. Cascade config locations depend on the installed version.
04
Verify the connection
Run the diagnostic below, then ask your agent: “Use Boolance’s get_connection_status tool.” A successful check confirms authentication and lists all seven tools.
Add your paths above to generate the connection check.Terminal commands use POSIX shell quoting (macOS / Linux). Windows users can run the same Node arguments with PowerShell quoting. Configurations support absolute Windows paths.
CLEAR BY DESIGNYour books.
Your books.
Your control.
The bridge makes authenticated GET requests through an explicit allowlist. No tool can post entries, move money, or change a transaction.
Understand the session.
The saved credential is a regular Boolance session with the same access and expiration as your sign-in. Read-only applies to this bridge’s tools; it is not a separately scoped API token.
Keep the report context.
Reports preserve currency, date range, posting basis, and readiness warnings. Your agent should surface incomplete or unreviewed records alongside the numbers.
Local today. Explicit about access.
This implementation uses stdio. There is no hosted MCP URL or OAuth flow. Your selected AI provider may receive tool results; configure that client’s permissions and data settings.
Code with the whole picture.
Give your next conversation a little more business context.
Find your agent