AI agent for ANAF (e-Factura, SAF-T)

Connect ANAF (e-Factura, SAF-T) to your AI agent through the WorkAist MCP server.

/ agents/marketplace

Marketplace

Pre-built connector templates · install with one click.

Connector
ANAF (e-Factura, SAF-T)
Production-grade accounting MCP server. AGPL-3.0, self-hosted.
v1.1.2accountingoauth
  1. 1Install in one click

    Pick ANAF (e-Factura, SAF-T) from the marketplace. WorkAist handles OAuth 2.0 and stores the credentials encrypted — no JSON keys to paste.

  2. 2Tools auto-generated

    ANAF (e-Factura, SAF-T) exposes 6 MCP tools to every agent in your workspace: list_invoices, create_invoice, get_balance, list_transactions, and more. Each tool is a typed function, not a brittle script.

  3. 3Data flows to your graph

    Historical accounting records sync to your private knowledge graph. Agents query relationships across all connected sources, not just ANAF (e-Factura, SAF-T) in isolation.

  4. 4Your agents take action

    Your AI agent picks the right tool, runs it under your access policies, and answers in plain language — with a full audit trail of every ANAF (e-Factura, SAF-T) call.

In 60 seconds

ANAF (e-Factura, SAF-T) is accounting software built for businesses in Romania you can connect to WorkAist in minutes. Through the open MCP standard, your AI agents categorise transactions, reconcile accounts and prepare reports — autonomously, under explicit permissions, with no manual hand-offs. ANAF (e-Factura, SAF-T) authenticates via OAuth, and because WorkAist is self-hosted under AGPL-3.0, your data never leaves your own infrastructure.

Authentication & setup

The ANAF (e-Factura, SAF-T) connector authenticates via OAuth 2.0.

One-click OAuth setup

WorkAist redirects you to the provider, you authorize, and the access token is encrypted and stored. No keys to copy.

Frequently paired with ANAF (e-Factura, SAF-T)

FAQ

Can a WorkAist AI agent really automate ANAF (e-Factura, SAF-T) end-to-end?

Yes. The connector exposes read and write tools through Model Context Protocol. AI agents call them through plain-language instructions in a CLAUDE.md file — no glue code.

How does this differ from using the ANAF (e-Factura, SAF-T) API directly?

The connector adds permission isolation, audit logging, cost tracking per agent, and reversible PII redaction at the LLM boundary. It also presents ANAF (e-Factura, SAF-T) as part of a unified Knowledge Graph alongside your other tools.

What does it cost?

WorkAist is open-source under AGPL-3.0 and self-hosted, so the connector itself is free. You pay only for ANAF (e-Factura, SAF-T)'s own API costs (if any) and the LLM tokens your agent consumes.

Is my ANAF (e-Factura, SAF-T) data sent to a third party?

No. WorkAist runs in your own infrastructure. Data flows from ANAF (e-Factura, SAF-T) → your WorkAist instance → the LLM you choose. Sensitive fields can be tokenized before reaching the LLM.

What if ANAF (e-Factura, SAF-T) changes its API?

The connector is versioned and published openly. When ANAF (e-Factura, SAF-T) ships breaking changes, we bump the connector version and the marketplace UI surfaces the upgrade as a one-click apply.

Licensed under AGPL-3.0 · Self-hosted, your data stays yours.