Skip to main content
Glama
pete-life

Billy MCP

by pete-life
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Billy MCP

No user-submitted related servers found.

    Related Servers

    • Billy MCP Server

      markhm
      A
      license
      A
      quality
      D
      maintenance
      Integrates Billy's accounting system with MCP, providing tools to manage invoices, contacts, products, payments, and more via natural language.
      15
      2
      MIT

    • kitsas-mcp

      Valtterios
      F
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to read local Kitsas bookkeeping files, including accounts, fiscal years, partners, and vouchers, and to create purchase invoice drafts from chat or PDFs without ever writing to the ledger.
      10
      -

    • billy-mcp

      Cimalys
      A
      license
      B
      quality
      D
      maintenance
      An MCP server for Danish accounting via Billy.dk API, enabling natural-language control over invoices, bank lines, reports, and more, with a write-guard for safety.
      65
      1
      MIT

    • mcp-business-docs

      mittalmayank842
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to search and inspect an invoice ledger, generate VAT summaries, run OCR on local documents, and use reusable prompts for chasing overdue invoices and reconciling entries.
      2
      -

    • billy-mcp

      Thourum
      A
      license
      A
      quality
      B
      maintenance
      Connects AI assistants to the Danish accounting platform Billy (billy.dk) for managing invoices, journal entries, balances, and receipts, with built-in human approval for all write operations.
      40
      28 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct action or resource: read/list, status, receipt import/list, vendor save/list, and proposal lifecycle (prepare/plan/refresh/execute/journal). Although plan and journal both deal with proposals, plan is single-proposal inspection and journal is a history listing, so boundaries remain clear.

    Naming Consistency4/5

    All tools share the billy_ prefix and use straightforward action or resource names, but the set mixes verb forms (billy_list, billy_get, billy_prepare) with noun forms for list/status operations (billy_status, billy_receipts, billy_vendors, billy_journal). This is a minor consistency issue, not a confusing one.

    Tool Count5/5

    13 tools is well within the ideal range and each tool maps to a distinct step in the workflow: reading, status, receipt archive, vendor registry, and the prepare/plan/refresh/execute proposal pipeline. There is no obvious tool that is redundant or missing at the count level.

    Completeness4/5

    The proposal pipeline covers prepare, inspect, refresh, execute, and journal, and the read/import/list tools cover most inputs and outputs. The main gaps are a lack of an explicit cancel/abandon operation for proposals and no direct tool for uploading receipts into Billy; agents can usually work around these via execute attachments and by ignoring rejected proposals.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources