Claude (MCP)
The MCP endpoint lets a user question their NomaUBL instance from Claude Desktop, Claude Code or a claude.ai connector, under their own account: invoices and their history, validation errors, e-reporting, dashboards and period figures, the server log, the settings, the documentation. Invoices and e-reporting runs are those of the user's companies and data scope, as in the lists of the application. It is read-only unless the instance allows changes, off by default, and it needs a valid licence.
What goes to Anthropic in that case, and what does not, is described on Data sent to Anthropic.
At a glance
Turn it on
In Settings → Global → AI, group MCP server (this editor is in English in the application):
| Field | Default | Description |
|---|---|---|
| MCP endpoint | N | The instance answers at /mcp, for the users whose role has MCP access. |
| Allow changes over MCP | N | Claude may save analyses, mappings and documents when the user asks — see Changes. Off: read only. |
Sign-in must be enabled on the instance: Claude always acts as a named user.
Behind a reverse proxy, fill in Public address in Settings → Global → Authentication: the sign-in from Claude uses it, as the password reset links do.
Who may connect
Only the roles that have the MCP access feature (Roles, tab Access) can connect Claude; no role has it by default. The other grants of the role then decide what Claude reaches:
| Tools | The role needs |
|---|---|
| Invoices, errors, lifecycle, e-reporting, dashboards, period figures, documentation | MCP access. Invoices and e-reporting runs are limited to the companies and the row filters of the role. |
| Server log | The Server log page. |
| IT dashboard | The IT dashboard page. |
| Data Explorer — model, fields, aggregations, saved analyses | The Explorer page. |
| PDF to XML conversion of a sample | The Process Document page, or Settings access. |
| Implementation report; setup review — configuration objects, configuration check, scheduled jobs, rule sets, licence state, system —; mapping work | Settings access. |
A role without a list of allowed pages reaches every page. An invoice outside the user's scope is answered as not found.
Connect Claude
The server address, the tokens and the extension are in the Claude (MCP) tab of the profile window (the user button of the top bar).
| Way | For | Steps |
|---|---|---|
| Claude Desktop extension | Claude Desktop, including for an instance that is not reachable from the internet. | Extension downloads a .mcpb file. Open it with Claude Desktop: the server address is already filled in, and the extension asks for the personal token. Nothing else to install. |
| Sign-in from the client | Claude Code; a claude.ai connector when the instance is reachable from the internet. | Give the client the Server address only. The browser opens NomaUBL: sign in as usual (password or SSO), then on Connect Claude to NomaUBL choose 30, 90 or 365 days and click Allow (or Refuse). |
| Pasted token | Claude Code, a script. | Create a token, copy it — shown once, copy it now — and give it to the client as the request header Authorization: Bearer <token>. |
The extension has four settings in Claude Desktop: NomaUBL address, Personal token, Samples folder (optional — the only folder Claude may send files from) and Accept an internal certificate (for a self-signed or company certificate). They are in the language of the interface the extension was downloaded from.
The extension carries the environment and the address of its instance in its name — NomaUBL – prod · nomaubl.example.com — so the extensions of several instances install side by side, each with its own token. Claude is told which instance it is talking to and says which one an answer concerns.
| Answer of the endpoint | Meaning |
|---|---|
404 | The MCP endpoint is off. |
401 | No token, or a token that is unknown, expired or revoked. |
403 | The role has no MCP access, or the instance has no valid licence. |
Tokens
Your tokens lists the user's tokens and the accesses opened by a sign-in from Claude. Each line gives its origin — the name of the client the access was allowed for, or created here for a token created in this tab — and its creation and expiry dates; Revoke ends one at once. A token is valid 30, 90 or 365 days.
A password change — by the user or by an administrator — and the deactivation of the account remove the user's tokens: an account enabled again starts without any. A token also stops working when the role loses MCP access.
The server keeps a fingerprint of the token, never the token itself.
What Claude can do
| Subject | Claude can |
|---|---|
| Invoices | List invoices, read one in full (header, lines, VAT, validation errors, lifecycle with the platform's reasons), list the e-reporting runs. |
| Figures | Read the Billing overview, Statistics, Operations and IT dashboard figures and the summary of a period. |
| Data Explorer | Run any aggregation of the Explorer — grouping, measures, filters, period, Top N — and the saved analyses. |
| Diagnosis | Read the server log, the integrity checks, the status and reason codes, the e-directory, and follow the diagnostic playbooks. |
| Setup review | Read the configuration objects, the configuration check, the scheduled jobs, the rule sets, the licence state and the settings — secrets are never shown. |
| Documentation | Search and read the NomaUBL documentation and the implementation report of the instance. |
| Samples and mapping | Read the structure of an XML sample, convert a PDF sample with a document's settings, propose and check a mapping — see below. |
A result longer than 60,000 characters is cut, and Claude is asked to narrow its request.
Sample files
A customer's XML or PDF can be given to Claude to work on:
- from the profile window: Sample files tab, button Add;
- from Claude Desktop, which sends a file of the Samples folder chosen in the extension's settings, and of no other folder, when the user asks it to work on one.
Samples are .xml or .pdf files of 20 MB at most, 50 per user, kept 7 days and then removed by the server. They are working copies of one user: they are never processed as invoices nor sent to the platform.
The Sample files tab is shown to every user, with or without MCP access: a file attached in the AI assistant is listed there too, and deleted there.
With a sample, Claude reads the structure of an XML, or converts a PDF with a document's settings and tries table anchors without saving. With Settings access it also does the mapping work of the XSL editor: it proposes the mapping of a sample (and, for a text PDF, the extraction rules), reads a document's saved mapping and the variables its rule set requires, checks a mapping on a sample and shows the UBL it gives. The sample follows the steps of a real run: a PDF converted as a text PDF or a JD Edwards PDF according to the document, the pre-processing stylesheet, the split into invoices, the sign inversion. Nothing is saved: Claude gives the values to enter in the mapping editor.
Changes
With Allow changes over MCP, Claude can, when the user asks:
| Change | The role needs |
|---|---|
| Save an Explorer analysis. | The Explorer page. |
| Save mapping values in a document's stylesheet. | Settings access. |
| Save a document's PDF to XML settings. | Settings access. |
| Create a document — by source: XML, PDF, UBL or connector, with its own blank stylesheet or from an existing one — or update its settings. | Settings access. |
Each source keeps its own rules: text PDF settings are refused on a JD Edwards document and the reverse, and a UBL document has no mapping. Passwords, tokens and keys cannot be set this way. The previous version stays in the file history or the configuration history, and every change is written to the server log with the user's name. Claude asks the user before a call that changes something.
Usage
The AI usage view of Diagnostics lists the calls made from Claude under the channel Claude (MCP) — by user, by day and by tool, with those that failed and those that saved a change. The server log holds one line per failed call and one per change; a successful read leaves no line.
Tips & best practices
- Grant MCP access to a dedicated role first. The grants of the role are what Claude reaches: the Explorer page and Settings access open the corresponding tools.
- Keep Allow changes over MCP off on production until the mapping work is finished on a test instance; Promotion then carries the result.
- Prefer the extension for an internal server. A claude.ai connector is called from the internet; the extension calls the instance from the user's computer.
- Revoke rather than wait. A token no longer used is ended from the profile in one click.