Cortena exposes an MCP server so you can query payables from an LLM client (Claude, ChatGPT, Dust, Cursor, Perplexity, and similar).
Security & permissions for IT reviewers: MCP server security overview.
Typical use
List invoices, check Pulse metrics, inspect approval queues, and (when allowed) prepare approval or review actions that you confirm before anything changes. Read-only connectors stay read-only; read + write connectors still need your explicit confirmation for invoice workflow writes.
Setup
- Ask a tenant admin to grant MCP access under Settings → User permissions.
- Prefer Claude from the directory when you can: open Cortena FinOps in the Claude directory, click Connect, and sign in to Cortena. Claude registers via DCR automatically.
- Or, for other assistants that support DCR: give them only
https://app.cortena.ai/api/mcp
The assistant creates the OAuth Client ID and Secret itself. You sign in to Cortena and finish connector setup (access mode and allowed tenants) in the browser. - If your assistant does not support DCR, open Settings → MCP access (beta) (
https://app.cortena.ai/?settings=mcp-access), create an OAuth client, choose Read only or Read + write plus allowed tenants, and paste the Client ID and Secret into the assistant. - Complete Cortena sign-in when prompted.
Treat a manually copied OAuth Client Secret like a password.
Remove access anytime
You can delete MCP credentials and disconnect assistants at any time from Settings → MCP access (beta). Use Revoke on the client row (including auto-registered connectors). Existing tokens stop working on the next request.
Writes
Invoice and workflow changes use prepare → you confirm → commit. Payables upload (when permitted) uses the same ingest path as manual upload in Cortena and does not push into DATEV by itself.
Full capability, permission, DATEV, and audit detail: MCP server security overview.