Skip to main content
Glama
kentaroajisaka

mf-full-mcp

Related Servers

Alternatives to mf-full-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      -
    • A
      license
      B
      quality
      D
      maintenance
      An MCP server that integrates with MoneyForward Cloud Invoice API v3 to automate the creation and management of quotes and invoices. It supports Japanese invoice system compliance, allowing users to handle partners, items, and billing through natural language.
      22
      3 npm
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Unofficial, community-maintained stdio MCP server for Money Forward ME that uses cookie-based authentication to retrieve accounts and assets from manual entry accounts.
      14
      25 npm
      5
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      An unofficial MCP server that integrates with the hokan Insurance CRM API v2 to manage customer data, schedules, and tasks. It also features specialized tools for Japanese insurance law compliance, including intent confirmation and regulatory check generation.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server and Claude plugin that enables interaction with freee APIs for accounting, human resources, invoicing, and more. It provides secure OAuth 2.0 authentication and integrates detailed API reference skills to support tasks like creating invoices and managing company data through natural language.
      5,036 npm
      504
      Apache 2.0

    TDQS

    B3/5.0

    Scored across 29 tools

    Disambiguation4/5

    Most tools have clear resource/action separation: journals, transactions, reports, master data, auth, and office management each have distinct targets. A few pairs like currentOffice vs list_offices or postJournals vs postTransactionJournalize have some boundary overlap, but the descriptions are precise enough to resolve most ambiguity.

    Naming Consistency3/5

    The dominant mfc_ca_get/post/put/delete + Resource pattern is readable and consistent within the core accounting tools. However, the server mixes styles: verbless mfc_ca_currentOffice, un-prefixed snake_case names like remove_office and list_offices, and bare verbs like authenticate.

    Tool Count2/5

    29 tools is a heavy surface and exceeds the 25+ threshold. Although the tools are grouped into clear subdomains such as journals, reports, master data, and auth, the high number of parallel getters and report variants creates meaningful selection overhead for agents.

    Completeness3/5

    Core workflows are well covered: authentication, office switching, journal CRUD, report retrieval, and master data reads are all present. Obvious gaps remain, however: trade partners have no update/delete, transactions have no update/delete, and vouchers lack list/get or an attach-orphan recovery path.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues