Alegra MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALEGRA_USER | Yes | The email address associated with your Alegra account. | |
| ALEGRA_TOKEN | Yes | Your Alegra API secret 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| AlegraAPIC | Una herramienta para interactuar con la API de contabilidad de Alegra. Permite realizar operaciones CRUD en una amplia gama de recursos como Facturas, Contactos, Items, Notas de Crédito, Órdenes de Compra y muchos más. |
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 ambiguity or overlap between tools. The single tool clearly handles all operations for the Alegra accounting API, so agents cannot misselect between multiple options.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'AlegraAPI' follows a clear and descriptive pattern, and there are no other tools to compare it against for inconsistency.
The server has only one tool, which is too few for the stated purpose of handling CRUD operations on a wide range of resources like invoices, contacts, items, credit notes, and purchase orders. A single tool for such a broad domain forces agents to handle complex parameter parsing and lacks the granularity needed for effective tool use.
While the single tool claims to cover all CRUD operations for many resources, this monolithic approach creates significant gaps in the tool surface. Agents will struggle with dead ends due to the lack of specific tools for distinct operations (e.g., separate create_invoice, get_contact tools), making the surface incomplete for reliable agent workflows.