Skip to main content
Glama
NightSquawk

invoiceninja-mcp-server

by NightSquawk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to invoiceninja-mcp-server

No user-submitted related servers found.

    Related Servers

    • Cin7 Core Meta MCP Server

      tzenderman
      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

    • FreshBooks MCP Server

      zeal-tristian-chevier
      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.
      -

    • QuickFile MCP Server

      marcusquinn
      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.
      76 npm
      4
      MIT

    • @indica-facil/mcp-chatwoot

      indicafacil-ai
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes the full Chatwoot API as 129 tools for AI assistants, enabling account, contact, conversation, message, inbox, team, report, help center, automation, and custom attribute management, plus exclusive Kanban and scheduled message features.
      13 npm
      MIT

    • NinjaOne MCP Server

      JDelgadoCMG
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables management of NinjaOne devices, organizations, alerts, and tickets through natural language, using a navigation-based tool selection for efficient interaction.
      Apache 2.0
    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

    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

    ActivitySlowing
    ResponsivenessNo issues

    Resources