Agent integrations · MCP
Connect your AI assistant to VatForge
VatForge speaks Model Context Protocol — the standard Claude Desktop, ChatGPT Connectors and Cursor use to reach external tools. Connect once and ask your own VAT data questions in plain English.
Read-only, scoped to your own account. The AI can query — it cannot file, disconnect, or change anything.
30-second explainer
What is MCP?
Model Context Protocol is an open standard that lets an AI assistant call tools on a server you authorise. You add VatForge's endpoint to your assistant, sign in once, and from then on the assistant can read the specific VatForge data you approved — nothing else, and nothing belonging to anyone else.
Authentication is OAuth 2.1 with dynamic client registration (RFC 7591), so there is no API key to paste or leak, and access can be withdrawn at any time.
Try asking
- “What's my OSS threshold status for 2026?”
- “Which platforms do I have connected?”
- “Show me my recent transactions to Germany”
- “Which countries generated the most revenue this quarter?”
- “Have I generated any OSS returns yet?”
What VatForge exposes
Four read-only tools
That is the whole surface. Consent is bundle-level — approving grants read access to all four as one unit.
get_threshold_summary
Your OSS distance-sales threshold position for a given year.
Running total in EUR, percentage of the threshold used, whether OSS is required.
list_platform_connections
Which revenue platforms you have connected.
Platform, connection method, status and sync timestamps. No API keys, tokens or webhook secrets.
list_transactions
Your recent transactions, with optional date range and country filter.
Buyer country, buyer type, amounts, VAT amount and rate, source platform. Never buyer name, email or address.
list_oss_returns
The OSS VAT returns you have generated.
Quarter, status, transaction count, total taxable amount and total VAT.
What it cannot do
- File or submit an OSS return.
- Connect or disconnect a revenue platform.
- Create, edit or delete a transaction.
- Change any setting, plan or account detail.
- See another VatForge customer's data — Row-Level Security scopes every query to your account.
- See your buyers' names, email addresses or postal addresses.
Your customers' personal details are not exposed. list_transactions returns country + type + amounts only — never buyer name, email, or address. Platform credentials, OAuth tokens and webhook secrets are never returned by any tool.
Setup
Add the endpoint to your client
You need a VatForge account and an MCP-capable client. The endpoint is the same everywhere:
https://dauwhfzlvuvcxmiquaee.supabase.co/functions/v1/mcpClaude Desktop
Preferred route — Settings → Connectors → Add custom connector, then paste the endpoint and complete the sign-in. Claude's connector UI changed during 2026, so we describe it in words rather than shipping a screenshot that goes stale.
Config-file route (Windows and macOS)
- Settings → Developer → Edit Config
- Open claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json)
- Add the block below
- Save, then fully quit Claude Desktop (tray icon → Quit, or ⌘Q) and reopen — the config only reloads on a full restart
{
"mcpServers": {
"vatforge": {
"url": "https://dauwhfzlvuvcxmiquaee.supabase.co/functions/v1/mcp"
}
}
}ChatGPT
Connectors are available on paid ChatGPT plans; the Free tier does not support them.
- Open ChatGPT in the browser
- Settings → Connectors → Add connector
- Paste the VatForge endpoint above
- Complete the sign-in and approve the consent screen
Cursor
- Settings → MCP → Add server
- Paste the VatForge endpoint
- Complete the sign-in and approve the consent screen
Any other MCP client
Any client that supports remote MCP servers over Streamable HTTP with OAuth 2.1 can connect. Dynamic client registration (RFC 7591) is supported, so there is no key to issue by hand.
{
"mcpServers": {
"vatforge": {
"url": "https://dauwhfzlvuvcxmiquaee.supabase.co/functions/v1/mcp",
"transport": "http"
}
}
}What happens next
The sign-in and consent flow
- 01Your client opens a browser tab pointing at VatForge.
- 02You sign in, if you are not already signed in.
- 03The consent screen names the client asking for access and what it may read.
- 04You approve — or deny, and nothing is granted.
- 05The browser hands a token back to your client.
- 06You can query. Start with one of the sample questions above.
Troubleshooting
If something doesn't connect
Revoking access
Withdraw access at any time
Revocation is a right, not a favour (GDPR Art. 7(3)). There are three routes today.
In your AI client
Remove the VatForge connector — Claude Desktop → Connectors, ChatGPT → Settings → Connectors, Cursor → Settings → MCP. The client stops holding a token immediately.
In VatForge
Settings → Integrations shows the Agent integrations (MCP) card with the endpoint and these revoke instructions. Per-client revoke buttons inside VatForge are not shipped yet.
Server-side
Email hello@vatforge.com and we invalidate the token server-side, across every client.