Skip to main content
Glama
Aslan11

temporal-invoice-mcp

by Aslan11
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to temporal-invoice-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      -

    • mcp-ledger-server

      grzegorzkowalskigk-jpg
      F
      license
      A
      quality
      B
      maintenance
      Exposes a ledger system (invoice queue, duplicate control, VAT register, contractor history, decision journal) as MCP tools for AI agents, enabling accurate invoice processing with deterministic validation.
      7
      -

    • agent-invoice

      nyx-builds
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to generate, track, and manage invoices via MCP tools, with CLI support for payment tracking and earnings summaries.
      MIT

    • invox-mcp

      Edgetive
      F
      license
      Not graded
      quality
      D
      maintenance
      Hosted MCP server that enables AI assistants to manage clients, invoices, and expenses via the Invox API, supporting actions like drafting, sending, cancelling, and marking invoices as paid, as well as logging expenses and updating client information.
      -

    • myinvois-mcp

      techtemplemy
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables issuing and managing validated Malaysian e-invoices via MyInvois (LHDN) directly from MCP clients, with tools for TIN validation, invoice drafting, submission, and document management.
      20 npm
      2
      Do What The F*ck You Want To Public
    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

    C2.9/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: starting the workflow, checking status, approving, or rejecting. No overlap or ambiguity among the four tools.

    Naming Consistency4/5

    Three tools follow a verb_noun pattern (approve_invoice, process_invoice, reject_invoice), while invoice_status is noun_noun. However, all use consistent snake_case and are clear and descriptive.

    Tool Count5/5

    Four tools is perfectly appropriate for a simple invoice approval workflow: start, approve, reject, and check status. The scope is well-scoped without being too sparse or excessive.

    Completeness4/5

    The tools cover the core lifecycle of an invoice workflow (create, approve, reject, status). Minor gaps like update or cancel are not critical for a basic approval process.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources