Skip to main content
Glama
kentaroajisaka

mf-api-mcp

by kentaroajisaka
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mf-api-mcp

No user-submitted related servers found.

    Related Servers

    • mf-accounting-voucher-mcp

      solara-co-jp
      F
      license
      A
      quality
      C
      maintenance
      Enables attaching and detaching voucher files and deleting journal entries in Money Forward Cloud Accounting via its REST API v3, complementing the official MCP server.
      3
      -

    • moneyforward-connector

      knorq-ai
      A
      license
      C
      quality
      C
      maintenance
      Enables AI assistants to operate MoneyForward Cloud Invoice, Expense, and Accounting through their public APIs, exposing 56 tools for issuing invoices, filing expenses with receipt images, and posting journal entries.
      56
      11 npm
      MIT

    • Qonto MCP Server

      j-about
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Qonto's Business API for banking operations. Supports all API key-accessible endpoints for managing business banking transactions and account information.
      3
      MIT

    • bokio-mcp

      diblaze
      F
      license
      B
      quality
      B
      maintenance
      Enables interaction with the Bokio accounting API for managing journal entries, invoices, customers, items, and more, with read-only mode by default for safety.
      18
      -

    • freee会計 MCP Server

      tsurutan
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to access and manage accounting data through the freee accounting API, supporting operations like transaction management, financial analysis, and account item management.
      280 npm
      1
      -
    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

    C2.7/5.0

    Scored across 26 tools

    Disambiguation4/5

    Most tools map to a distinct resource/action, and the Japanese descriptions generally clarify the boundaries between journals, transactions, reports, and master data. A few pairs could still be confused, such as `postJournals` vs `postTransactionJournalize` and `getJournals` vs `getTransactions`, and `deleteVouchers` is misleading since it only unlinks rather than deletes a voucher.

    Naming Consistency3/5

    The domain tools mostly follow a readable `mfc_ca_{HTTP verb}{Resource}` camelCase pattern, but the top-level utilities use a different snake_case style (`list_offices`, `auth_status`, `mf_api_info`). There are also odd deviations like `mfc_ca_currentOffice` with no verb and awkward report names such as `getReportsTrialBalanceBalanceSheet`.

    Tool Count2/5

    26 tools is above the 25-tool threshold and feels heavy for a flat MCP surface. While most tools are individually distinct, several read-only master-data and report endpoints could be consolidated, making tool selection harder for an agent.

    Completeness3/5

    Core journal workflows are well covered with create, read, list, update, and delete, plus reports and transaction journalization. However, there are notable lifecycle gaps: trade partners and other master data are mostly read-only or create-only, vouchers cannot be listed or reattached after unlinking, and `postVouchers` can create orphan vouchers with no later attachment path.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources