Skip to main content
Glama
saiganeshreddy7

AutoFYI MCP

by saiganeshreddy7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to AutoFYI MCP

No user-submitted related servers found.

    Related Servers

    • expense-tracker-mcp-server

      SINGH-HARSH1
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables users to manage personal finances using natural language, including tracking expenses, income, budgets, and generating financial summaries.
      -

    • Secure Billing MCP Server

      PuneetChandel
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables secure interaction with billing systems through comprehensive PII/PCI redaction, field allowlisting, and multi-layer security controls. Protects sensitive financial data while providing LLMs safe access to account, subscription, and invoice information.
      -

    • dingdawg-finance-agent

      dingdawg
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to perform financial analysis, budget forecasting, compliance checks, expense categorization, and risk assessment, returning structured JSON with audit-ready governance receipts.
      5
      40 npm
      1
      Business Source 1.1

    • fincon

      Abishai95141
      F
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to perform financial reconciliation with a deterministic proof engine: intake files, match transactions, verify proofs, resolve exceptions, and sign off on balanced journals under the user's authority.
      21
      -

    • xero-mcp

      hritikff
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables natural-language interaction with Xero accounting data, including invoices and intents, with role-based access control and audit trail.
      146 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.6/5.0

    Scored across 18 tools

    Disambiguation3/5

    Most tools have distinct purposes, but search_clients and find_client both handle client lookup with ranked candidates, and get_client_jobs_to_invoice and get_jobs_and_interim_table overlap in reading live FYI jobs. Descriptions help clarify the differences, but an agent could still misselect in some situations.

    Naming Consistency4/5

    Tool names generally follow a consistent verb_noun pattern (describe_, get_, prepare_, etc.), with only autofyi_health deviating from the pattern. Minor inconsistencies like singular vs plural (client vs clients) are present but do not cause confusion.

    Tool Count4/5

    At 18 tools, the set is slightly above the ideal 3-15 range, but each tool serves a distinct step in the billing workflow—from discovery and planning to preparation and execution. The count is justified by the complexity of the domain and the safe execution paradigm.

    Completeness4/5

    The tool set covers the full lifecycle for the intended use case: reading client data, inspecting billing state, planning, preparing, canceling, and executing actions. Obvious gaps include a lack of a tool to list all prepared actions, but the core workflows are well covered.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources