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.
      69 PyPI
      20
      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 341 tools

    Disambiguation2/5

    With 341 tools spanning overlapping domains, many tools have unclear boundaries: invoices_submit vs einvoice_submit, declarations_submit vs declarations_file_via_agent vs agent_submit_declaration_pdf, and multiple sync/status tools (anaf_sync_trigger, anaf_sync_status, spv_sync_prepare, declarations_sync). Even with detailed descriptions, an agent would frequently struggle to pick the right tool for a task.

    Naming Consistency3/5

    Most tools follow a resource_verb pattern (invoices_list, clients_create, webhooks_delete), but there are notable deviations: some use verb-first (auth_login, balance_list, import_get), some use bare nouns (borderou_providers, document_types, agent_status), and some mix conventions (spv_sync_agent_result vs spv_document_upload, dosare_d212_prefill vs dosare_c168_create). The pattern is readable but not consistently applied.

    Tool Count1/5

    341 tools is an extreme count for any MCP server. While the server covers a broad ERP/accounting domain, the sheer number creates overwhelming selection complexity and suggests the entire REST API surface was exposed without curation. This is far beyond the typical well-scoped MCP server.

    Completeness4/5

    The tool surface is remarkably comprehensive for the domain: invoices, proformas, delivery notes, receipts, clients, suppliers, products, payments, VAT, declarations, SPV, dosare, webhooks, backups, imports, exports, and admin functions are all covered with full lifecycle operations. Minor gaps exist (e.g., no explicit tool for updating invoice line items after issue, no direct SPV request cancellation), but the coverage is extensive.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources