ARCA Invoice MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CUIL | Yes | Your ARCA CUIL number used for authentication. | |
| PASS | Yes | Your ARCA password used for authentication. | |
| ARCA_HEADLESS | No | Set to '1' to run Chrome in headless mode. Only use after validating that ARCA accepts the environment. | 0 |
| ARCA_CHROME_PATH | No | Path to the Google Chrome executable. Overrides the default Chrome path on macOS. | |
| ARCA_AUTH_FALLBACK | No | Enables browser fallback for authentication when direct HTTP fails. Use 'headless' for headless Chrome or 'visible' to show the browser. Disabled by default. |
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 |
|---|---|
| arca_prepare_invoiceA | Prepare a Factura C through direct HTTP calls to official ARCA RCEL. Authentication is direct HTTP by default, with browser fallback only when explicitly configured. This tool never issues the invoice. Show the preview and obtain explicit approval before calling arca_issue_invoice. |
| arca_issue_invoiceA | Irreversibly issue the currently prepared invoice. Call only after showing the preview and receiving explicit user approval. Never retry automatically after an uncertain response. |
| arca_list_invoicesA | Read issued Factura C records from official ARCA RCEL for a date range. This tool is read-only and does not include unissued previews. |
| arca_discard_prepared_invoiceB | Close the current preview without issuing an invoice. |
| arca_invoice_statusA | Read whether the local ARCA session has a prepared invoice. Does not mutate ARCA. |
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 5 tools
Each tool covers a distinct action: prepare, issue, list, discard, and status. These lifecycle stages are clearly separated, so an agent can unambiguously select the correct tool for a given need.
Four of the five tools follow the arca_verb_noun pattern (arca_prepare_invoice, arca_issue_invoice, arca_list_invoices, arca_discard_prepared_invoice). However, arca_invoice_status breaks this pattern by using a noun-like 'status' instead of a verb, causing a minor inconsistency.
With 5 tools, the server is well-scoped for its invoice lifecycle purpose. Each tool earns its place without redundancy or bloat, fitting the ideal 3-15 range.
The lifecycle of prepare, issue, discard, list, and local status covers the core workflow. However, after an uncertain issue response, there is no direct tool to verify the invoice status on the ARCA side (list_invoices requires knowing the date range and may not be real-time), leaving a minor gap in uncertainty resolution.