Back to MCP directory
publicPublicdnsLocal runtime

ledger-mcp-server

一种MCP服务器,通过提供账户列表、余额查询和交易登记查看功能,允许通过克劳德访问和管理账本文件。

article

README

ledger-service MCP server

MCP Server for accessing and managing ledger files through Claude.

Components

Tools

The server implements three tools for ledger management:

  • list-accounts: Lists all accounts in the ledger

    • Takes "year" as a required argument
    • Returns formatted list of all available accounts
  • account-balance: Gets the balance for a specific account

    • Takes "year" and "account" as required arguments
    • Returns the current balance for the specified account
  • account-register: Shows the transaction register for an account

    • Takes "year" and "account" as required arguments
    • Returns detailed transaction history for the specified account

Installation

Prerequisites

  • Python 3.13 or higher
  • uv package manager
  • Node.js and npm (for debugging)

Install from PyPI

uv pip install ledger-service

Debugging

Using the inspector to debug the server:

npx @modelcontextprotocol/inspector 
  uv 
  --directory /path/to/ledger-service 
  run 
  ledger-service

MCP Inspector debugging interface

Configure Claude Desktop

Add the server configuration to Claude Desktop's config file:

On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json On Windows: %APPDATA%/Claude/claude_desktop_config.json

Development Configuration
"mcpServers": {
  "ledger-service": {
    "command": "uv",
    "args": [
      "--directory",
      "/path/to/ledger-service",
      "run",
      "ledger-service"
    ]
  }
}
Production Configuration
"mcpServers": {
  "ledger-service": {
    "command": "uvx",
    "args": [
      "ledger-service"
    ]
  }
}

Development

Local Setup

  1. Clone the repository
  2. Create and activate a virtual environment
  3. Install dependencies:

The base path can be configured by modifying the LEDGER_BASE_PATH constant in server.py.

License

GNU GENERAL PUBLIC LICENSE Version 3, 29 June 2007

help

Runtime guide

cloud

Hosted runtime

Hosted servers run from a provider-managed environment. You usually connect the MCP client to the hosted endpoint or follow the provider's authorization flow, without keeping a local process alive

  1. Open provider connection page
  2. Authorize or copy endpoint
  3. Connect from your MCP client
terminal

Local runtime / other methods

Local servers run on your own machine or infrastructure. You normally copy the server_config into your MCP client, install the required package, and provide env variables from env_schema when needed

  1. Copy server_config
  2. Install required package
  3. Fill env variables and restart client