InvoicePDFs MCP Server
OfficialRelated Servers
Alternatives to InvoicePDFs MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI agents to perform go-to-market workflows such as company and contact enrichment, CRM querying, and controlled, audited writes to a CRM through MCP tools callable from any MCP client.1MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to securely call enterprise MCP tools with tenant-scoped RBAC, human approvals, audit logging, and multi-tool workflows across customer, order, document, and ticket data.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents such as ChatGPT, Claude, and local LLMs to operate an enterprise digital-operations platform through MCP, exposing 19 model tools and 3 app-only tools for identity, data, workflow, files, and PII-controlled operations with role-based permissions and two-phase confirmations.Apache 2.0
- FlicenseAqualityCmaintenanceEnables AI agents to discover and query enterprise knowledge documents and business metrics through standardized MCP tools, supporting retrieval, structured sales/order analysis, anomaly scanning, and data lineage lookups.12-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to access a unified catalog of tools from various APIs (OpenAPI, GraphQL, MCP, Google Discovery) through the MCP protocol.12 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible agents such as Claude Desktop and Cursor to process invoices, list pending reviews, retrieve case details and risk signals, decide approvals or rejections, access masked vendor master data, and view AP dashboard metrics while resuming paused LangGraph workflows.MIT
TDQS
Scored across 30 tools
Most tools target a distinct resource+action, but a cluster of stateless operations (document_render, document_render_stored, document_calculate, document_validate, compliance_check, compliance_xml) all act on a document body and overlap conceptually, and document_send vs document_transition-to-'sent' needs the description to separate. The problem is compounded because descriptions point to tools that don't exist under those names (create_document_render, render_document, list_generated_invoices), which will actively mislead selection.
The tool names themselves mostly follow a consistent noun_verb pattern (document_create, customer_list, recurring_pause), which is readable. However, the descriptions repeatedly reference aliases that are not the actual tool names (render_document, calculate_document, resume_recurring_invoice, list_recurring_invoices), so the naming is not self-consistent across names and docs.
At 30 tools this is heavy for the scope, pushing past the point where an agent can comfortably scan the set. While the invoicing domain is genuinely broad, several render/validate/compliance variants and a generic find_operation/call_operation escape hatch could likely be consolidated.
Core lifecycle is well covered: document create/get/list/update/duplicate/transition, customers, recurring schedules, rendering, sending, and compliance. There are minor gaps (no customer or business_profile delete, business_profile only list/create, templates only list), but the find_operation/call_operation pair provides an escape hatch to the rest of the API.