e-conomic MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ECONOMIC_DEBUG | No | Set to 'true' to emit JSON debug logs to stderr. | false |
| ECONOMIC_BASE_URL | No | Base URL for e-conomic API. | https://restapi.e-conomic.com |
| ECONOMIC_APP_SECRET_TOKEN | Yes | Your e-conomic app secret token. | |
| ECONOMIC_AGREEMENT_GRANT_TOKEN | Yes | Your e-conomic agreement grant token. |
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 |
|---|---|
| helloA | Return a friendly greeting. |
| list_customersA | Fetch a page of customers from the e-conomic API. |
| get_customerA | Fetch a single customer by customer number. |
| list_productsA | Fetch a page of products. |
| upsert_productB | Create or update a product by productNumber. |
| create_invoice_draftC | Create a draft invoice in e-conomic. |
| update_invoice_draftC | Update an existing draft invoice in e-conomic. |
| update_customerC | Update an existing customer in e-conomic. |
| list_invoice_draftsB | Fetch a page of draft invoices. |
| get_invoice_draftA | Fetch a draft invoice by number. |
| book_invoice_draftC | Book a draft invoice into a booked invoice. |
| list_booked_invoicesB | Fetch a page of booked invoices. |
| get_booked_invoiceA | Fetch a booked invoice by number. |
| download_invoice_pdfA | Download a booked invoice PDF as base64. |
| list_payment_termsA | Fetch a page of payment terms. |
| list_customer_groupsA | Fetch a page of customer groups. |
| list_vat_zonesB | Fetch a page of VAT zones. |
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 17 tools
Each tool targets a distinct resource-action pair: customers, products, invoice drafts, booked invoices, and reference data. List vs. get operations are clearly separated, and even the 'hello' tool is unambiguous.
Tools consistently use verb_noun snake_case (list_, get_, create_, update_, book_, download_, upsert_). The only outlier is 'hello', which breaks the pattern but is a trivial helper.
At 17 tools, this is slightly above the typical 3-15 range, but the count is justified by covering customers, products, invoices, and reference data. No tool feels redundant.
The invoice workflow is well covered from draft creation through booking to PDF download. However, customers lack a create operation and products lack a single get operation, leaving minor gaps.