Skip to main content
Glama
NightSquawk

invoiceninja-mcp-server

by NightSquawk

Related Servers

Alternatives to invoiceninja-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Connects AI assistants to an Invoice Ninja v5 instance so users can query clients, invoices, quotes, payments, expenses, dashboard totals, and 25+ native reports in natural language. It runs read-only by default with opt-in writes, secret and bearer-link redaction, and LLM-friendly Markdown or compact JSON output.
      34
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients like Claude Desktop to interact with Invoice Ninja v5, providing tools to read and write contacts, customers, quotes, projects, products, and optionally invoices, with configurable permissions.
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI to dynamically discover and invoke any Cin7 Core API endpoint using three generic tools (list, describe, invoke) plus a bug-report tool, covering the entire API surface without predefined endpoints.
      4
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides 29 tools for Claude to query and update FreshBooks directly, including invoices, clients, estimates, expenses, payments, timesheets, and reports.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to interact with QuickFile UK accounting software, providing access to invoicing, client management, purchases, banking, and financial reporting through 40+ tools covering the complete QuickFile API.
      149 npm
      4
      MIT

    TDQS

    A4.3/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clear, distinct role: list_endpoints for discovery, describe_endpoint for details, and call_endpoint for execution. No overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case (list_endpoints, describe_endpoint, call_endpoint), making the pattern predictable.

    Tool Count4/5

    With only 3 tools, the set is minimal but well-suited for its meta-API exploration purpose. The count feels slightly low but efficient for the intended workflow.

    Completeness5/5

    The tool set covers the full lifecycle of API interaction: discover endpoints, inspect parameters, and execute calls. There are no missing operations for this domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues