Your AI assistant, connected to your invoicing
Every workspace has its own MCP (Model Context Protocol) server. Claude, or any MCP-compatible client, can look up your documents, customers and reports, and prepare drafts on your behalf with the permissions you approve.
Connection details
| Field | Value |
|---|---|
| URL | https://tuempresa.factura.com.do/mcp |
| Transport | Streamable HTTP, stateless |
| Authentication | OAuth 2.1. factura.com.do is the authorization server for your subdomain, with dynamic client registration: the assistant registers itself, no keys to copy |
| Token scope | Your subdomain only: one company's token doesn't work against another |
| Revocation | Takes effect on the next request. Deactivating a user also cuts off their assistant |
| Compatible clients | Any MCP client with OAuth and dynamic registration that receives the code at an https URL or at http://127.0.0.1 (not localhost). From a browser, only Claude's origin is allowed today |
How to connect Claude
- In Claude, open Settings → Connectors and add a custom connector with your MCP server URL.
- Claude takes you to your workspace sign-in page. Sign in with your user.
- Review the consent screen: it shows the app asking for access, the site the access goes to and each permission. If your session is older than 10 minutes, it asks for your password again.
- Approve. From then on the assistant acts as you, with the permissions granted.
In Claude Code, add the same server from the terminal:
claude mcp add --transport http factura https://tuempresa.factura.com.do/mcpWhat it can do
The server exposes more than 60 tools, grouped like this:
| Look up | Invoices, credit and debit notes, expenses, quotations, delivery notes, consignments and received documents; customers, suppliers and products; payments, fiscal reports, sales and purchases report, dashboard, exchange rate and RNC lookup. |
|---|---|
| Prepare | Draft invoices, quotations, credit notes, debit notes and expenses; clone or convert documents; create and edit customers, suppliers and products; record payments. |
| Publish and void | Publish a draft (assigns the e-NCF and uses a sequence number) and void invoices and expenses. These permissions are requested separately, on their own consent screen. |
| Send | Email a document. It has its own permission because it sends company data outside. |
| Modules | Accounting, inventory and treasury, only if your company has the module. Journal entries and adjustments stay as drafts; posting them is another permission. |
Permissions
Permissions follow the resource:action shape. Read and draft permissions are requested when you connect; those with fiscal or external effect (documents:issue, documents:void, documents:send) are requested only when needed, on their own consent screen.
| Permission | What it allows |
|---|---|
documents:read · clients:read · suppliers:read · products:read · payments:read · expenses:read · reports:read · catalogs:read | Read |
documents:write · expenses:write | Create and edit drafts |
clients:write · suppliers:write · products:write · payments:write | Create and edit master data; record payments |
documents:issue | Publish a draft (irreversible) |
documents:void | Void |
documents:send | Send by email |
accounting:* · inventory:* · treasury:* | Installed modules: read, write and, for accounting and inventory, post |
What it doesn't do
- It doesn't sign or submit documents to the DGII. Publishing leaves the document ready; a person submits it to the DGII from the app.
- A published draft can't be edited: it can only be voided, and voiding uses another sequence number.
- No elicitation: the server doesn't ask the assistant to prompt you mid-operation. Confirmation lives on the server side (drafts and typed confirmations).