Beancount.io vs Companies House

In-depth architectural comparison of the Beancount.io and Companies House MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

B

Choose Beancount.io when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: BQL ledger queries, Accounting report access, Ledger-file editing.

Explore Beancount.io Details

Choose Companies House when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• You have access to required keys: COMPANIES_HOUSE_API_KEY.
• Primary tools included: Company and officer search, Company profiles and statutory records, Ownership, appointments and disqualification lookup.

Feature & Specification Comparison

Specification	B Beancount.io Developer Tools	Companies House Developer Tools
Summary
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

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

{
  "mcpServers": {
    "companies-house": {
      "command": "npx",
      "args": [
        "-y",
        "companies-house-mcp"
      ],
      "env": {
        "COMPANIES_HOUSE_API_KEY": "YOUR_COMPANIES_HOUSE_API_KEY_HERE"
      }
    }
  }
}

Related MCP Server Comparisons