Skip to main content
Glama
stornoro

Storno CLI

Official
by stornoro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

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.
      3
      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
      C
      maintenance
      Enables integration with Fatture in Cloud to manage Italian electronic invoices through natural conversation, including creating, sending, and tracking invoices and financial data.
      51 PyPI
      25
      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.4/5.0

    Scored across 374 tools

    Disambiguation3/5

    Most tools are scoped to a clear resource and action, and the descriptions are detailed enough to separate similar operations. However, the sheer number produces several near-overlapping flows (companies_select vs companies_set_active, declarations_submit vs declarations_file_via_agent vs agent_submit_declaration_pdf, retired declarations_sync vs spv_sync_prepare) that an agent can easily misselect.

    Naming Consistency3/5

    Names mostly follow a resource_action snake_case pattern, but prefixes mix singular and plural forms (company_registry_search vs clients_list, product_categories_list), and some tools are noun phrases rather than verb-led (dashboard_stats, balance_analysis, fiscal_calendar). The surface remains readable but is not fully predictable at 374 tools.

    Tool Count1/5

    374 tools is an extreme mismatch for a single MCP server, far beyond the 50+ threshold for severe overload. Even for a large ERP, this many tools overwhelms selection and violates the principle that each tool should clearly earn its place in a focused set.

    Completeness5/5

    The surface covers full lifecycle operations for invoices, proformas, delivery notes, receipts, payments, clients, suppliers, bank/cash registers, VAT, declarations, SPV, e-Factura, e-Transport, imports/exports, backups, admin, webhooks, and licensing. Almost every domain an agent would need is represented, with only intentional constraints such as sync-only product creation.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources