Taggun MCP server
15 operations0 webhooks
Scan receipts and invoices into structured data with Taggun's OCR API, and validate them against campaign rules or rules sent with the request.
Try Taggun with your agent
Connect Taggun, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.
Using Corsair, show me what you can do in Taggun on my account, then run one read-only example and show me the result.
Taggun tools and triggers
Tools are what your agent can do in Taggun through Corsair's MCP server. Triggers are the Taggun events a routine can start from.
Campaigns
- CreateWrite
Store a new set of validation rules under a campaign ID you choose; rejected if that ID already exists
campaigns.create
- DeleteDestructive
Remove a campaign's validation rules permanently; later submissions against that campaign cannot evaluate them
campaigns.delete
- GetRead-only
Read one campaign's stored validation rules; sections with no rules may be omitted from the answer
campaigns.get
- ListRead-only
List the campaign IDs that have validation settings stored on the account; needs the Campaign Validation feature
campaigns.list
- UpdateDestructive
Replace a campaign's stored validation rules wholesale: every section left out is removed, so re-send the response from `campaigns.get` with your changes
campaigns.update
- Validate FileWrite
Check an uploaded receipt against a campaign's stored rules and return pass/fail per rule; a failed rule is a successful call reporting `successful: false`
campaigns.validateFile
- Validate UrlWrite
Check a receipt at an HTTPS URL against a campaign's stored rules; a failed rule is a successful call reporting `successful: false`
campaigns.validateUrl
Simple
- EncodedWrite
Scan a base64-encoded receipt or invoice and return the four core fields; each call is one billable scan
simple.encoded
- FileWrite
Scan an uploaded receipt or invoice file and return the four core fields; each call is one billable scan
simple.file
- UrlWrite
Scan a receipt at an HTTPS URL and return the four core fields with confidence levels; each call is one billable scan and the receipt is stored unless `incognito` is set
simple.url
Verbose
- EncodedWrite
Scan a base64-encoded receipt or invoice and return the full extraction, including product line items unless `extractLineItems` is false
verbose.encoded
- FileWrite
Scan an uploaded receipt or invoice file and return the full extraction, including product line items unless `extractLineItems` is false
verbose.file
- UrlWrite
Scan a receipt at an HTTPS URL and return the full extraction: line items, text, helper arrays, per-field confidence and enabled feature blocks
verbose.url
Receipt Validation
- FileWrite
Check an uploaded receipt against rules sent with this request, storing nothing; a failed rule is a successful call reporting `successful: false`
receiptValidation.file
- UrlWrite
Check a receipt at an HTTPS URL against rules sent with this request, storing nothing; a failed rule is a successful call reporting `successful: false`
receiptValidation.url
Connect Taggun to Claude, ChatGPT or Cursor
- 1
Connect Taggun in Corsair
Add your Taggun API key once in Corsair. Corsair stores the credential encrypted and makes the Taggun API calls for your agent, so it never goes into a prompt or a config file. Connect Taggun
If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Taggun. On a ChatGPT personal plan, connect Taggun here first.
- 2
Add Corsair's MCP server to your agent
Every client uses the same address:
https://mcp.corsair.dev/mcpOpen Customize → Connectors → Add custom connector, paste the address, then select Connect.Add a custom MCP server with the address and choose OAuth. Personal plans get read tools only.Add to CursorOr add this to~/.cursor/mcp.json. Cursor opens Corsair to sign in the first time it connects.{ "mcpServers": { "corsair": { "url": "https://mcp.corsair.dev/mcp" } } }Run this, then run/mcpin Claude Code to sign in.claude mcp add --transport http corsair https://mcp.corsair.dev/mcpCodex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client
- 3
Sign in and choose what needs your approval
Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Taggun's read and write operations run right away and its 2 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.
FAQ
Install corsair and @corsair-dev/taggun, add the Taggun plugin, and connect with an API key. Then call methods like corsair.taggun.api.campaigns.create() from your app. Corsair keeps each tenant isolated.
Yes. Taggun requires an API key from your Taggun account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.
Yes. One Corsair client can hit Taggun, GitHub, Notion, Stripe, and the rest. Trigger Taggun from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.
Teams use Corsair for scan receipts and invoices into structured data with Taggun's OCR API, and validate them against campaign rules or rules sent with the request. Common builds include sync jobs, admin tooling, and agents that call Taggun APIs from your backend.
The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Taggun API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.
We maintain @corsair-dev/taggun in the open repo. When Taggun ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.
No. Corsair does not read your Taggun data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Taggun data on your behalf.
Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.
Yes. Put Taggun on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 2 destructive Taggun operations. You can change a link's mode at hub.corsair.dev/me.