factura-uz-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FACTURA_CLIENT_ID | Yes | OAuth2 client ID from Factura.uz | |
| FACTURA_CLIENT_SECRET | Yes | OAuth2 client secret |
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 |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_invoiceB | Create an electronic invoice (e-factura). |
| sign_invoiceC | Sign an invoice with digital signature. |
| get_invoiceA | Get invoice details by ID. |
| list_invoicesC | List invoices with filters. |
| accept_invoiceB | Accept a received invoice. |
| reject_invoiceA | Reject a received invoice. |
| get_company_by_innB | Look up company by INN (tax ID). |
| list_productsB | Search product catalog. |
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 8 tools
Each tool maps to a distinct action or resource: invoice lifecycle actions (create, sign, get, list, accept, reject) are mutually exclusive, and company/product lookups are clearly separate. No two tools overlap in purpose.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_invoice, list_products). The verbs are clear and uniform, with no mixed conventions or vague phrasing.
Eight tools is well-scoped for an e-invoicing server, covering core operations without redundancy. The count feels neither sparse nor overwhelming for the domain.
The set covers the main invoice lifecycle (create, sign, retrieve, list, accept/reject) plus necessary lookups (company, products). A minor gap exists—no update or cancel/void operation for invoices—but core workflows can be completed without it.