Skip to main content
Glama
Accounting Ledger MCP Server

Accounting Ledger MCP Server

by dougdaley

Accounting Ledger Model Context Protocol Server

A Model Context Protocol (MCP) server that provides accounting ledger creation, transaction and reporting capabilities using the MCP Python SDK and Python Accounting library.

Overview

This MCP server enables AI assistants to interact with a double-entry accounting system, allowing for:

  • Creating accounting entities including the chart of accounts, currencies, and tax codes

  • Recording various types of transactions (cash sales, cash purchases, supplier invoices, customer bills)

  • Generating financial reports (profit & loss statements)

Related MCP server: postledger

šŸ“¹ Demo Video

Watch the MCP Accounting Ledger Server in action:

This demo shows the complete workflow from setup to creating ledgers, recording transactions, and generating reports using the MCP server with Claude Desktop.

Features

šŸ¢ Entity Management

  • Create accounting entities with default configuration (companies/organizations)

šŸ’° Transaction Recording

  • Cash Sales: Record immediate revenue transactions

  • Cash Purchases: Record immediate expense transactions

  • Client Invoices: Create receivable transactions

  • Supplier Bills: Create payable transactions

šŸ“Š Financial Reporting

  • Generate profit & loss statements

  • Customizable date ranges for reports

šŸ”§ Built-in Tools

  • Echo tool for testing connectivity

  • Comprehensive error handling

  • SQLite database backend

Installation

This project uses UV for dependency management. Make sure you have UV installed on your system.

Prerequisites

Install uv

Setup

  1. Clone the repository: Clone this repository locally and update config.toml with the path to your local project

  2. Create the virtual environment:

    uv venv
  3. Activate the virtual environment:

    source .venv/bin/activate
  4. Install dependencies:

    uv sync

Running the Server

Development Mode

To run the server in development mode:

uv run mcp dev server.py

This will start the server the MCP Inspector which is a useful tool for testing and debugging the MCP server. To access the MCP Inspector navigate to http://localhost:6274.

Testing in Claude Desktop

After installing Claude Desktop add the MCP server to it by running:

uv run mcp install server.py

After running this command open Claude Desktop. There will most likely be an error with the MCP server. Open Claude Desktop settings, navigate to Developer, select our MCP Server (My Ledger) and click Edit Config. Open the JSON configuration file and update the command and args values as shown (replacing path_to_server with the path to the server on your local machine).

{
  "mcpServers": {
    "My Ledger": {
      "command": "/path_to_server/.venv/bin/python",
      "args": [
        "/path_to_server/server.py"
      ]
    }
  }
}

Now restart Claude Desktop and the MCP server should be working.

Available Tools

Tool

Description

Parameters

echo

Test connectivity

message: str

create_ledger

Set up new accounting entity

entity_name: str

record_cash_sale

Record cash sale transaction

narration: str, amount: float, quantity: int, tax_code: str, entity_name: str

record_cash_purchase

Record cash purchase transaction

narration: str, amount: float, quantity: int, tax_code: str, entity_name: str

record_client_invoice

Create client invoice

narration: str, amount: float, quantity: int, tax_code: str, entity_name: str

record_supplier_bill

Create supplier bill

narration: str, amount: float, quantity: int, tax_code: str, entity_name: str

generate_profit_loss_report

Generate P&L report

entity_name: str, start_date: str, end_date: str

Configuration

The server uses a config.toml file for configuration. Key settings include:

  • Database: SQLite database URL

  • Account Types: Chart of accounts configuration

  • Transaction Types: Available transaction types and prefixes

  • Tax Settings: Default tax codes and rates

  • Reporting: Report formatting and sections

Database Schema

The system uses the Python Accounting library's database schema, which includes:

  • Entities: Companies/organizations

  • Currencies: Supported currencies

  • Accounts: Chart of accounts with types

  • Taxes: Tax codes and rates

  • Transactions: Various transaction types

  • Line Items: Transaction details

Development

Project Structure

mcpServerDemo/
ā”œā”€ā”€ server.py              # Main MCP server implementation
ā”œā”€ā”€ main.py                # Entry point
ā”œā”€ā”€ pyproject.toml         # UV project configuration
ā”œā”€ā”€ config.toml            # Accounting system configuration
ā”œā”€ā”€ test_accounting.db     # SQLite database
└── python_accounting/     # Local Python Accounting library

Adding New Features

  1. Add new tools to server.py using the @mcp.tool() decorator

  2. Update the configuration in config.toml if needed

  3. Test using the MCP Inspector

  4. Update this README with new tool documentation

Dependencies

  • mcp[cli]: Model Context Protocol SDK

  • python-dateutil: Date parsing utilities

  • sqlalchemy: Database ORM

  • strenum: String enumerations

  • toml: Configuration file parsing

Available Tools

7 tools
create_ledgerB
Sets up the ledger by:
- Creating the SQLAlchemy engine from configuration.
- Running migrations to create tables.
- Creating a default reporting entity, currency, chart of accounts, and taxes if not present.

Inputs: entity_name (required).

echoA
Echoes the input message back to the user.

Args:
    message (str): The message to echo.

Inputs: message (required).

generate_profit_loss_reportA
Generates a Profit & Loss (Income Statement) report in JSON format.

Args:
    entity_name: Entity name to generate report for
    start_date: Start date for the report (YYYY-MM-DD format, optional)
    end_date: End date for the report (YYYY-MM-DD format, optional)

Returns:
    JSON string containing the P&L report

Inputs: end_date, start_date, entity_name.

record_cash_purchaseB
Records a cash purchase (expense) transaction.

Args:
    narration: Description of the purchase
    amount: Purchase amount (excluding tax)
    quantity: Quantity of items purchased
    tax_code: Tax code to apply (default: GSTIN)
    entity_name: Entity name to use

Inputs: amount (required), narration (required), quantity, tax_code, +1 more.

record_cash_saleA
Records a cash sale transaction.

Args:
    narration: Description of the sale
    amount: Sale amount (excluding tax)
    quantity: Quantity of items sold
    tax_code: Tax code to apply (default: GSTOUT)
    entity_name: Entity name to use

Inputs: amount (required), narration (required), quantity, tax_code, +1 more.

record_client_invoiceA
Records a client invoice (credit sale) transaction.

Args:
    narration: Description of the invoice
    amount: Invoice amount (excluding tax)
    quantity: Quantity of items invoiced
    tax_code: Tax code to apply (default: GSTOUT)
    entity_name: Entity name to use

Inputs: amount (required), narration (required), quantity, tax_code, +1 more.

record_supplier_billA
Records a supplier bill (credit purchase) transaction.

Args:
    narration: Description of the bill
    amount: Bill amount (excluding tax)
    quantity: Quantity of items billed
    tax_code: Tax code to apply (default: GSTIN)  
    entity_name: Entity name to use

Inputs: amount (required), narration (required), quantity, tax_code, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: setup, reporting, and four specific transaction types. The echo tool is unrelated but not confusing, as it serves a generic utility function.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern with snake_case (create_ledger, generate_profit_loss_report, record_*). The exception is 'echo', which is a simple verb, but this is a minor deviation.

    Tool Count5/5

    Seven tools is well-scoped for an accounting ledger server: one setup tool, four transaction recording tools, one reporting tool, and one utility. Each tool earns its place.

    Completeness3/5

    The server covers setup, transaction recording, and reporting, but lacks fundamental operations like listing or retrieving transactions, editing, or deleting records. This creates a gap where agents cannot inspect or manage recorded data directly.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Double-entry accounting ledger MCP server for autonomous agents that enables creating accounts, posting journal entries, and generating financial reports.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for double-entry bookkeeping with idempotent writes, immutable entries, and audit trail. Enables trustworthy financial recording and verification through natural language.
      31 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to operate a self-hosted financial platform over MCP, managing books, expenses, revenues, settlements, payments, accounts, categories, transfers, positions, and cash flow with idempotent and audited writes.
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables querying and managing a live accounting ledger, including transactions, balances, VAT summaries, deadlines, and documents, from any MCP client.
      86
      56 npm
      MIT