Parseur can connect directly to AI assistants like Claude, ChatGPT and Cursor through the Model Context Protocol (MCP). Once connected, you can manage mailboxes, upload documents, check parsing results, and set up exports — all by chatting with AI in plain English, without leaving your conversation to open the Parseur dashboard.
This article covers how to connect, what the integration can do, and a few common use cases to get you started.
What is MCP?
MCP (Model Context Protocol) is an open standard that lets AI assistants securely call external tools. When you connect the Parseur MCP server, the AI gains a set of "tools" it can use on your behalf — for example, listing your mailboxes, uploading a document for parsing, or generating an export link. It decides when to use these tools based on what you ask it to do, so there's no special syntax to learn.
Prerequisites
Before you start, make sure you have:
A Parseur account
An AI assistant that supports remote MCP servers / custom connectors (Claude, ChatGPT, Claude Code, Codex, Cursor, VS Code, etc.)
Permission to add connectors in your workspace (on team or enterprise plans, an admin may need to add or allow the connector first)
That's it — no API key to copy, nothing to install on your computer.
Connecting Parseur to your AI
Parseur hosts its MCP server for you. You add one URL to your AI assistant, sign in to Parseur, and approve access.
Parseur MCP server URL:
https://api.parseur.com/mcp
How it works
Add the URL above as a new connector / MCP server in your AI assistant.
Your assistant opens a Parseur sign-in page in your browser.
Log in to Parseur (email and password, or Sign in with Google) and click Approve.
You're sent back to your assistant, and Parseur's tools are ready to use.
Access is granted through OAuth, so your AI assistant never sees your password or API key. You can revoke access at any time by disconnecting the connector in your assistant.
Platform-specific instructions
Claude (web and desktop app)
Go to Settings → Connectors.
Type Parseur in the Search bar:
Click on Connect.
Sign in to Parseur and click Approve.
To use Parseur in a conversation, make sure the connector is enabled from the + (tools) menu in the chat box.
Team and Enterprise plans: an organization Owner first adds the Parseur connector under Organization settings → Connectors. Each member then connects it with their own Parseur account from Settings → Connectors.
More info: Parseur - Claude
Claude Code
Run:
claude mcp add --transport http parseur https://api.parseur.com/mcp
Then start Claude Code, type /mcp, select parseur and choose Authenticate. Your browser opens so you can sign in to Parseur and approve access.
More info: Claude Code MCP documentation
ChatGPT
Go to Settings → Plugins
Click on Browse directory
Click Add → Add Custom MCP Server:
Enter:
Name: Parseur
MCP Server URL:
https://api.parseur.com/mcpAuthentication: OAuth
Save, then sign in to Parseur and approve access when prompted by clicking Authorize:
More info: ChatGPT developer mode documentation
Codex
Run:
codex mcp add parseur --url https://api.parseur.com/mcp codex mcp login parseur
The login command opens your browser so you can sign in to Parseur and approve access.
Cursor
Open Settings → MCP (or Tools & Integrations) and click Add new MCP server. This opens your
mcp.jsonfile.Add:
JSON:
{ "mcpServers": { "parseur": { "url": "https://api.parseur.com/mcp" } } }Save. Cursor shows a Login / Needs authentication prompt next to the Parseur server — click it, sign in to Parseur and approve access.
More info: Cursor MCP documentation
VS Code (GitHub Copilot Chat)
Open the Command Palette and run MCP: Add Server, choose HTTP, and enter
https://api.parseur.com/mcpwith the nameparseur. Or add it manually to.vscode/mcp.json:
JSON:
{ "servers": { "parseur": { "type": "http", "url": "https://api.parseur.com/mcp" } } }Click Start above the server entry. VS Code asks you to sign in — approve access in the Parseur page that opens.
More info: VS Code MCP documentation
Other AI assistants
Any assistant that supports remote MCP servers over HTTP with OAuth can connect using https://api.parseur.com/mcp. Parseur supports OAuth discovery and dynamic client registration, so you don't need to create a client ID or secret.
Using an API key instead of OAuth
If your assistant or automation can't do OAuth (for example, a headless script or agent), you can authenticate with your Parseur API key instead by sending it as a header:
Authorization: Bearer YOUR_PARSEUR_API_KEY
Keep your API key secret — anyone with it has full access to your Parseur account.
What can you ask AI to do?
Here are some common use cases to try once you're connected:
1. Check on your mailboxes
"List my Parseur mailboxes sorted by document count." "How many documents did the Invoices mailbox process this week?"
2. Upload and parse a document
"Upload this receipt to my Receipts mailbox and tell me what data was extracted."
The AI will upload the file, wait for parsing to finish, and summarize the extracted fields.
3. Investigate a parsing issue
"Why did this document fail to parse? Show me the logs."
The AI can pull document-level processing logs to help you troubleshoot extraction errors.
4. Set up an export
"Create a CSV export for my Orders mailbox with the order number, date, and total fields."
5. Manage fields
"Add a new field called 'PO Number' to my Purchase Orders mailbox." "What fields does my Invoices mailbox currently extract?"
6. Automate with webhooks
"Set up a webhook so my Zapier flow gets notified whenever a document finishes processing in the Leads mailbox."
Tips
Be specific about which mailbox you mean. If you have several similarly named mailboxes, include the mailbox ID or exact name to avoid ambiguity.
Filter large mailboxes. Ask for e.g. "documents received this month" rather than the full history, since very large result sets can be slow to return.
Destructive actions (deleting a document, mailbox, or export config) will be confirmed with you before the AI executes them.
Multiple Parseur accounts? The connector uses whichever Parseur account you signed in with when you approved access. To switch, disconnect and reconnect while logged in to the other account.
Missing features? If there's a feature you need that we don't yet support, our AI will check against our feedback board and either upvote the missing feature if it's already been requested, or create a feature request on your behalf.
Troubleshooting
The sign-in page doesn't open, or I'm not sent back to my assistant.
Check that pop-ups aren't blocked, then try connecting again. Make sure you're signed in to the right Parseur account — and that your email address is confirmed — before clicking Approve.
The AI says it can't find any Parseur tools.
Check that the connector is connected and enabled (in Claude: Settings → Connectors, and the + menu in the chat box). If it shows as disconnected or needing authentication, click Connect again to re-authorize.
I previously set up Parseur with uvx and an API key, how do I switch over?
That local setup is no longer needed. Remove the parseur entry from your assistant's MCP configuration file (for Claude Desktop: Settings → Developer → Edit Config), restart the assistant, then follow the steps above. Keeping both can show duplicate Parseur tools.
A mailbox list comes back empty even though I have mailboxes.
Check that you approved access with the Parseur account that owns those mailboxes. If the problem persists, try asking the AI to fetch a specific mailbox by ID, and contact support at [email protected].
My data looks out of date.
Ask the AI to re-fetch. MCP calls are made live against your account, but the AI won't automatically refresh information already in the conversation unless asked.