oblio-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OBLIO_CIF | No | Default company CIF; can be changed at runtime with set_cif | |
| OBLIO_API_EMAIL | Yes | Oblio account email (Setari > Date Cont) | |
| OBLIO_API_SECRET | Yes | Oblio API secret (Setari > Date Cont) | |
| OBLIO_TOKEN_FILE | No | Path where the OAuth access token is persisted so it survives restarts (defaults to in-memory only) |
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_documentA | Issue a new fiscal document in Oblio: an invoice (factura), a proforma, or a delivery notice (aviz). Provide the document body (client, series, line items, dates). NOTE: Oblio has no draft state — the document is issued immediately. Pass an idempotencyKey to guard against accidental double-issue on retries. |
| get_documentA | Fetch a single document (invoice/proforma/notice) by its series name and number, including totals, status and a link. |
| list_documentsA | List documents of a given type, with optional filters: series, number, client, issue-date range, draft/cancelled flags, sorting and pagination. |
| cancel_documentA | Cancel (annul) a document. The document stays in Oblio marked as cancelled and can later be restored with restore_document. |
| restore_documentA | Restore a previously cancelled document back to its active state. |
| delete_documentA | Permanently delete a document. Oblio only allows deleting the last document in a series; prefer cancel_document for anything else. |
| collect_paymentA | Record a payment (incasare) against an existing invoice, identified by series name and number. The collect object specifies the payment method (Chitanta, Ordin de plata, Card, etc.) and optionally the amount and date; when no value is given the full remaining invoice amount is collected. Applies to invoices only. |
| get_nomenclaturesA | Fetch Oblio reference data: companies on the account, saved clients, products, VAT rates, document series, languages, or management units (gestiuni). Use this to discover valid values (e.g. series names, VAT rate names) before creating documents. Supports an optional name filter and extra query filters such as pagination offset. |
| create_einvoiceA | Submit an existing Oblio invoice to Romania's SPV (e-Factura). The invoice must already be issued in Oblio; this sends its XML to ANAF. The response includes an einvoice status: 0 = processing, 1 = success, 2 = errors, -1 = not sent. |
| get_einvoiceA | Fetch the SPV (e-Factura) status and archive for an invoice previously submitted with create_einvoice. Status codes: 0 = processing, 1 = success, 2 = errors, -1 = not sent. |
| set_cifA | Set the active company CIF used for all subsequent Oblio requests. Use this to switch between companies on the same Oblio account. |
| get_cifA | Return the company CIF currently used for Oblio requests. |
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 12 tools
Each tool has a clearly distinct purpose: document lifecycle (create, get, list, cancel, restore, delete, collect payment), e-invoice (create, get status), company configuration (get/set CIF, get nomenclatures). No overlapping functionality that would confuse an agent.
All tool names follow a consistent verb_noun pattern in lowercase_snake_case (e.g., cancel_document, create_einvoice, list_documents). No mixing of conventions or confusing abbreviations.
With 12 tools, the server is well-scoped for a document management system. Each tool covers a necessary operation without redundancy or excess. The count is appropriate for the domain.
The tool set covers the core lifecycle of fiscal documents: create, read, list, cancel, restore, delete, and payment collection, plus e-invoice integration. A minor gap is the lack of an update tool, but this is typical for fiscal documents that cannot be modified after issuance. Overall sufficiently complete.