Skip to main content
Glama
theluckystrike

mcp-statement-of-account

by theluckystrike
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to mcp-statement-of-account

No user-submitted related servers found.

    Related Servers

    • dunning-letters

      theluckystrike
      A
      license
      A
      quality
      B
      maintenance
      Enables users to track unpaid invoices and generate an escalating ladder of payment-reminder letters — first reminder, second reminder, and final notice — anchored to the due date, plus overdue listings, aging buckets, and a daily chase list of what to send today. It records payments and letters sent, rendering each letter as Markdown or printable HTML without ever emailing anything itself.
      11
      MIT

    • mcp-business-docs

      mittalmayank842
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to search and inspect an invoice ledger, generate VAT summaries, run OCR on local documents, and use reusable prompts for chasing overdue invoices and reconciling entries.
      2
      -

    • Xero Practice Aggregator MCP

      ppiotis
      A
      license
      A
      quality
      B
      maintenance
      Enables accountants and bookkeepers to ask practice-wide questions across every connected client Xero organisation in one read-only view — overdue invoices, payroll shortfalls, client health scores, trending-trouble lists and practice totals such as revenue and average DSO. It also generates ready-to-send Excel month-end packs per client, with every reported figure accompanied by the rule or formula that produced it and no financial data persisted to disk.
      12
      MIT

    • kelo-mcp

      solomonsalako
      A
      license
      Not graded
      quality
      C
      maintenance
      Lets a user ask what their business is owed, who to chase first, and get a chase email drafted in their own voice, via tools for weekly totals, chase queues, customer history, due-soon invoices and insights. Every tool only reads or returns a draft, so nothing can be sent.
      MIT
    • Kema Invoice MCP connector by Kema-Studio

      Kema Invoice MCP connectorofficial

      Kema-Studio
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to manage compliant e-invoicing (Factur-X, EN 16931) by creating, issuing, sending, and tracking invoices, quotes, and retainers through natural language via the Model Context Protocol.
      MIT

    • stripe-collections-mcp

      WayneChaney
      A
      license
      Not graded
      quality
      C
      maintenance
      Lets an MCP client find overdue Stripe invoices, see who owes what and how late they are, and re-send reminder emails for invoices that are still open. Runs read-only unless writes are explicitly enabled, re-checks invoice state before sending, and logs every call to an audit trail.
      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

    A4/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: license activation/status, dunning text, per-client aging, whole-book reporting, and statement building/PDF/text outputs. The descriptions explicitly cross-reference differences, such as statement_aging vs statements_report and statement_text vs statement_pdf, so there is no real ambiguity.

    Naming Consistency3/5

    Names are consistently snake_case and mostly use the statement_ prefix, but the verb/noun pattern is mixed: license_activate and statement_build are noun+verb, while license_status, statement_pdf, statement_text, and statements_report are noun+noun. The conventions are readable but not uniform enough for a higher score.

    Tool Count5/5

    Eight tools is well-scoped for this server: two license utilities, one dunning helper, two aging/report tools, and three statement output tools. Each tool earns its place and covers a distinct part of the statement workflow without redundancy.

    Completeness4/5

    The core statement workflow is well covered: build, text, PDF, aging, receivables report, dunning, and license state. Minor gaps exist, such as no license deactivation or quota/usage check for the free monthly statement builds, but these are workable and not likely to break common agent flows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources