Skip to main content
Glama
stornoro

Storno CLI

by stornoro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to Storno CLI

No user-submitted related servers found.

    Related Servers

    • SuperFaktura MCP Server

      Digitaliko
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with the SuperFaktura invoicing system for managing invoices, clients, and expenses via natural language.
      1
      Apache 2.0

    • Romania Invoice MCP

      junter1989k-ai
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to issue Romania e-Factura electronic invoices (factura electronica) into the national ANAF/SPV system by building UBL 2.1 CIUS-RO XML and uploading it under the merchant's own ANAF access token.
      MIT

    • Fatture in Cloud MCP Server

      aringad
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables integration with Fatture in Cloud to manage Italian electronic invoices through natural conversation, including creating, sending, and tracking invoices and financial data.
      52 PyPI
      23
      MIT

    • fic-mcp-payments-patch

      Deer412090
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables natural-language management of FattureInCloud invoicing, clients, suppliers, and e-invoice workflows, with extensions for marking invoices as paid and caching payment accounts/VAT types.
      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

    B3.1/5.0

    Scored across 367 tools

    Disambiguation2/5

    With 367 tools, there is substantial overlap and multiple paths to the same outcome: declarations can be created via declarations_create, declarations_upload, or declaration_build, and filed via declarations_submit, declarations_file_via_agent, agent_submit_declaration_pdf, or the two-step declarations_prepare/declarations_agent_result. Several retired and active sync/status tools also blur boundaries (declarations_refresh_statuses vs declarations_sync), making reliable tool selection difficult.

    Naming Consistency3/5

    The dominant pattern is domain_verb snake_case (invoices_list, clients_create, vehicles_update), which is mostly predictable. However, there are notable deviations: bare-noun tools like agent_certificates and cash_register_ledger, reversed constructions like defaults_invoice and client_statement, and phrase-style names like declarations_file_via_agent and invoices_share_links_revoke. The mixed conventions are readable but not consistently predictable at this scale.

    Tool Count1/5

    367 tools is an extreme mismatch for any MCP server surface. Even though the underlying platform is broad, exposing nearly 400 individually selectable tools creates an unmanageable discovery and selection burden for an agent, far beyond the 3-15 tool sweet spot. This should be aggressively grouped, consolidated, or split into multiple focused servers.

    Completeness4/5

    The surface is remarkably comprehensive, covering auth, companies, clients, suppliers, products, invoices, proformas, receipts, delivery notes, recurring billing, e-invoicing, declarations, dosare, expiries, vehicles, cash register, reports, imports/exports, webhooks, admin, and more. The main completeness issues are not missing major lifecycle operations but rather redundant and retired endpoints that create confusing dead ends within the declaration and sync workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources