Skip to main content
Glama
knorq-ai

moneyforward-connector

by knorq-ai

Related Servers

Alternatives to moneyforward-connector

No user-submitted related servers found.

    Related Servers

    • 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
    • -
      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.
      208
      1
      -
    • A
      license
      B
      quality
      D
      maintenance
      Lets AI agents create estimates/invoices, manage customers, and track payments on GooodBilling — a Japanese qualified-invoice (インボイス制度) compliant billing cloud.
      16
      18
      MIT
    • 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
      19,129
      3
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables individual proprietors and freelancers to manage daily accounting tasks like journal entries, invoice creation, and monthly reconciliation through simple tool calls, using freee's API.
      7
      15
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with the Tripletex accounting system via 56 tools and 18 skills for orders, invoices, bookkeeping, reports, projects, and travel expenses.
      23
      MIT

    TDQS

    C2.9/5.0

    Scored across 56 tools

    Disambiguation3/5

    Tools are organized by domain (quotes, billings, expenses, accounting) with consistent prefixes, but there is overlap: mf_create_billing and mf_create_billing_from_quote both create billings, and mf_convert_quote_to_billing vs mf_create_billing_from_quote likely do the same thing. Auth tools are duplicated across three API surfaces (root, expense, accounting), which could confuse an agent about which to use.

    Naming Consistency4/5

    Almost all tools follow a clear mf_<domain>_<verb>_<noun> pattern (e.g., mf_expense_create_transaction, mf_accounting_create_journal). A few root-level tools lack the domain prefix (mf_list_partners, mf_get_item), creating minor inconsistency, but the overall scheme is deterministic.

    Tool Count2/5

    56 tools is very heavy for a single connector, and the surface spans four distinct APIs (quotes/billings, expenses, accounting, auth) with duplicated auth machinery. A more modular design (one server per MF API) would reduce selection errors.

    Completeness3/5

    Core CRUD is mostly covered for billings, expenses, journals, and quotes, but there are gaps: no create/update for quotes' related entities (partners, items), no payment status listing/details, and one tool (mf_create_delivery_slip) is explicitly non-functional. The surface is broad but not consistently complete across sub-domains.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues