What the MCP server does
The server is the same ledger the dashboard uses, reached from Claude, Cursor, or another MCP client. Every request runs as the signed-in user, so a tool can read or write only what that user’s DualEntry role already allows. There is no shared integration user and no API key to mint. A connected client appears under Connected apps on the personal Security settings page, where you can revoke it.
To name a record, pass the record code shown on its page, such as
JE-0042, to get_record_by_number or as the code argument of search_records. Bare digits are treated as an internal ID. See Accounting Intelligence: Record Identifiers for the full lookup rules.
Guides
The full setup, tool catalog, and worked examples live alongside the accountant-facing docs. Start with a client connection, then use the tool catalog when you need permissions or troubleshooting.- Connect MCP Clients: one-click setup for Cursor and Claude, plus configuration blocks for VS Code, Codex, and other MCP clients.
- MCP Server: Tools, Permissions, and Troubleshooting: every tool by name, the permission it checks, and fixes for common connection errors.
- How to Connect Claude from the Connector Directory: the fastest path on Claude for web, desktop, and mobile.
- How to Post a Period-End Accrual from Claude: a worked example that writes back to the ledger with
save_record. - Accounting Intelligence: Record Identifiers: how MCP resolves the record code shown on a page.