# Beancount.io [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/bex-co/beancount-io  
**GitHub Stars:** 300  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/beancount-io

## Description
Query, edit, and reconcile a hosted Beancount ledger: BQL, reports, files, and bank imports.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "beancount-io": {
    "url": "https://your-deployment/api-gateway/mcp"
  }
}
```

## Documentation

## What Beancount.io MCP server does

The Beancount.io MCP server gives an MCP-compatible agent access to a hosted Beancount ledger. It is intended for working with plain-text accounting data while using the hosted service for ledger access and related workflows.

The supported scope covers five practical areas: querying ledger data with BQL, viewing reports, working with ledger files, importing bank data, and reconciling accounts or transactions. These capabilities make the server relevant to agents that need to answer questions about a ledger, inspect accounting output, or help maintain imported financial records.

Beancount.io is built around Beancount ledgers, whose underlying records remain readable plain text. The surrounding Beancount.io project also includes web and mobile clients, a Python CLI, reporting libraries, and agent-oriented skills, but this listing specifically describes the MCP access path to a hosted ledger.

## How it works

An agent uses MCP to request accounting operations from the Beancount.io service. Query requests can use BQL, while report-oriented requests expose generated or available financial views. File operations provide a way to inspect or modify ledger content, and bank-import functionality supports bringing external transaction data into the ledger.

Reconciliation is included for workflows that compare ledger records with imported or external bank information. The available description does not specify the exact request schemas, authentication flow, transport, or confirmation behavior, so those details should be verified in the repository before deployment.

## Tools and capabilities

The Beancount.io MCP server is described as supporting:

- BQL queries against a hosted ledger
- Access to accounting reports
- Reading or editing ledger files
- Bank-data import workflows
- Reconciliation of ledger information

These capabilities suit tasks such as finding transactions, reviewing financial summaries, updating entries, importing bank exports, and checking whether recorded data agrees with bank information. The material does not provide individual MCP tool names or parameter definitions, so this page does not infer them.

## Limitations and notes

The Beancount.io MCP server is described for a hosted Beancount ledger. The supplied material does not establish that this MCP interface works directly with local `.bean` files, although the broader Beancount.io project separately supports local-first workflows through its CLI and skills.

No environment variables, installation command, authentication variable names, supported MCP transports, or named desktop and coding clients are provided in the supplied material. Developers should consult the repository for those implementation details before configuring an agent.

The project is MIT licensed according to the repository README. Its broader codebase includes hosted and self-hosted components, but the listing does not state which deployment modes are available specifically for the MCP server.

_Full upstream README: https://allmcps.com/mcp/beancount-io/readme_