TAGGUN integrationTAGGUN logo

TAGGUN integration for AI agents.

TAGGUN integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves TAGGUN tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.

What your agents can do

Real TAGGUN actions, managed and audited.

Your user connects TAGGUN once; your agent can then tAGGUN offers a receipt OCR API with intelligent receipt processing — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.

  1. 1

    Your user grants TAGGUN access once (OAuth) — the token lands in the vault.

  2. 2

    Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.

  3. 3

    Every routed call appends a hash-chained audit record — nothing leaves your infra.

Tools & triggers

Supported TAGGUN tools.

0 tools are generated from the published TAGGUN catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.

Showing 0 tools. All published catalog entries are included in this page's server-rendered HTML.

No tools match “”.

FAQ

TAGGUN integration, answered

How do AI agents use TAGGUN through Open Connector?
Your user connects TAGGUN once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes TAGGUN tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
Is this a TAGGUN MCP server?
Yes. Open Connector can serve TAGGUN as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call TAGGUN actions with credentials injected server-side.
Where do TAGGUN credentials live?
In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

Give your agents TAGGUN — keep the keys.

Open source, self-hostable, with TAGGUN credentials that never leave your infrastructure. Run it from source today.