On this page
AI agents
What the MCP server is
The Ledger17 MCP server exposes the command API and query API — and only those two — as tools over the Model Context Protocol. An AI client connects once, authenticates with OAuth2, and can then read balances, drill into transaction lines, generate reports and record balanced transaction blocks on the caller’s behalf.
Nothing is widened and nothing is bypassed: every tool call is forwarded to the regular APIs with the caller’s own token, so the permission model applies unchanged. The admin API is deliberately not exposed.
Two ways to authenticate
| Situation | Credential | Tenant |
|---|---|---|
| A person uses an assistant interactively | Their own Ledger17 login (OAuth flow in the client) | Chosen in conversation if they belong to several |
| An agent runs unattended | An API key | Bound to one tenant — never chosen |
In this section
- The MCP server — endpoint, transport, authorization, and every tool it exposes.
- Connect a client — set up Claude.ai, Claude Code or an autonomous agent, and what to check when it doesn’t work.