Alegra

Alegra is the cloud platform you run your business on: electronic invoicing, contacts, inventory, bank accounts and accounting in one place. The official Alegra connector is a hosted MCP server (https://mcp.alegra.com/mcp), published by Alegra on its developer portal, that connects your agent to your business operation — in the official docs' words, it "permite acceso a herramientas de gestión empresarial como inventarios, contactos, facturas, bancos, pagos, retenciones, entre otros" (gives access to business-management tools such as inventory, contacts, invoices, banks, payments, retentions, among others).

Ask "How much did I invoice this month, and to which customers?" and the agent reads your invoices and builds the summary for you. "What stock do I have for each product?" comes straight from inventory, no screen-hunting. It also works for you: "Update Ana Gómez's phone number in her contact details" or "Register the payment I received for invoice 245." Everything lands in your Alegra account, under the same credential you use to access the API.

What you can ask

• "How much did I invoice this month, and to which customers?"
• "Show me the available stock for each product."
• "List my contacts and update Ana Gómez's phone number."
• "How much do I owe, and how much am I owed?"
• "Show me this month's income statement."
• "Register the payment I received for invoice 245."

What token you need

You need your Alegra API user token, converted to Base64 — the same token the Alegra API uses, in the format the MCP server expects.

1. Sign in to app.alegra.com. Top right, click Configuración (Settings) and open the API - Integraciones con otros sistemas section (API — integrations with other systems). That screen shows the email you use for API access and your token; if you don't have a token yet, you can generate one right there.
2. The server expects the credential as email:token encoded in Base64. The docs' own worked example: Authorization: Basic ZWplbXBsb2FwaUBhbGVncmEuY29tOnRva2VuZWplbXBsb2FwaTEyMzQ1, where that string is base64('<ejemploapi@alegra.com>:tokenejemploapi12345').
3. Encode your own email:token on your computer — never paste access credentials into a "Base64 encoder" website. On the macOS or Linux Terminal: printf 'email:token' | base64. On Windows (PowerShell): [Convert]::ToBase64String([Text.Encoding]::UTF8.GetBytes('email:token')).
4. Paste the resulting string when TerminalSync asks for ALEGRA_API_TOKEN_BASE64. It's stored encrypted in the app's Secrets and sent to the server as the Authorization: Basic … header Alegra expects.

Honest disclosure: this is a server hosted by Alegra (https://mcp.alegra.com), not something running on your computer — your requests travel to Alegra's server, which answers with data from your account. It reads and writes: it can create and update invoices, contacts, products and payments, and the documented catalog also includes delete tools (for example, deleting an invoice or a contact). What the agent can do is bounded by your token — the same access your Alegra user has through the API — and the MCP docs describe no server-side confirmation step. The Alegra API documents a usage limit of 150 requests per minute per user; beyond that it answers with a 429 error until the minute rolls over. The data comes from your account, and verifying it is your responsibility.