Skip to main content
Glama
kogasura

freee-mcp-solo

by kogasura
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to freee-mcp-solo

No user-submitted related servers found.

    Related Servers

    • mcp-server-freee

      wengbin21
      A
      license
      C
      quality
      D
      maintenance
      Enables AI agents to interact with the freee accounting API, offering tools for managing deals, invoices, partners, trial balance, and more via natural language.
      21
      MIT

    • 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.
      221 npm
      1
      -

    • freee Accounting MCP Server

      knishioka
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to interact with freee accounting software API for managing companies, transactions, invoices, and reports via OAuth authentication.
      60
      5,036 npm
      3
      MIT

    • freee MCP Server

      Unson-LLC
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to interact with freee accounting software through OAuth 2.0 authentication, supporting operations like transaction creation, account management, receipt uploads, and financial statement retrieval.
      MIT

    • 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
      97 npm
      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.8/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct resource/action: authentication, unprocessed transactions, deal creation, monthly summary, deal listing, invoice creation, and invoice listing. There is no overlap or ambiguity among them.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (create_deal, list_deals, create_invoice, list_invoices), but authenticate, pending_transactions, and monthly_summary deviate. The naming is still readable and consistently snake_case, so only minor deviations.

    Tool Count5/5

    Seven tools is well within the ideal 3-15 range and covers the server's accounting scope without unnecessary bloat. Each tool serves a clear purpose.

    Completeness3/5

    Core create/list workflows exist for deals and invoices, but there are no update or delete operations for either entity. This is a notable gap that could leave agents unable to correct errors or manage drafts fully.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources