Invoices Generator MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Host configuration (Not applicable/Optional) | |
| PORT | No | Port configuration (Not applicable/Optional) | |
| API_KEY | Yes | API 密钥 (API Key for authentication) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_invoiceC | Quickly generate invoices through a REST API endpoint |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The single tool 'generate_invoice' has a clear and distinct purpose that cannot be mistaken for any other tool in this set.
The naming is perfectly consistent as there is only one tool. It follows a verb_noun pattern ('generate_invoice'), which is clear and predictable, with no deviations or mixed conventions to evaluate.
A single tool is too few for a server named 'Invoices Generator MCP Server', which implies a broader scope for invoice management. While the tool 'generate_invoice' is core, the lack of related tools (e.g., for listing, updating, or deleting invoices) makes the set feel thin and incomplete for the apparent domain.
The tool set is severely incomplete for invoice generation and management. It only provides a generation tool, with no coverage for other essential operations like retrieving, updating, listing, or deleting invoices, which are typical in such domains and necessary for agent workflows.