Parseur
Parseur is an AI-powered data extraction tool that automates the parsing of emails, PDFs, and other documents into structured data.
Verdict
Common use cases
- Audit parsed invoices before pushing to accounting
- Check which mailboxes have active webhooks
- Pause a webhook during system maintenance
- List recent support tickets extracted from email
- Verify template coverage across mailboxes
Integration
- Vendor
- Parseur
- Category
- docs
- Auth
- API_KEY
- Tools
- 10
- Composio slug
parseur
Tools
- Create webhook
Tool to create a new webhook in parseur. use when you need to send parsed data via http post in real time.
- Delete webhookdestructive
Tool to delete a specific webhook. use when permanently removing a webhook after confirming its id.
- Enable webhook
Tool to enable a paused webhook for a mailbox. use after confirming the webhook is correctly configured.
- List Documents in Mailbox
Tool to list documents within a specific mailbox. use when you need to paginate, search, or sort the documents of a given mailbox after obtaining its id.
- List Mailboxes
Tool to retrieve a list of all mailboxes. use when you need to browse or filter mailboxes via pagination, searching, or sorting.
- List Templates for Mailbox
Tool to list all templates in a given mailbox. use after fetching mailbox details when you need to page through and inspect available templates for further actions.
- List Webhooks for Mailbox
Tool to list all webhooks for a mailbox. use when you need to retrieve both active and paused webhooks for a given mailbox.
- Pause webhook
Tool to pause (disable) an existing webhook. use when you need to stop sending parsed data via a webhook after confirming the correct mailbox and webhook ids.
- Retrieve a webhook
Tool to retrieve details of a specific webhook. use after creating or listing webhooks.
- Update webhook
Tool to update an existing webhook’s settings. use when you need to change the webhook’s target url, event type, headers, or name after creation.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Search for Parseur in the MCP directory and click Connect. 3. You'll be prompted to paste an API key; generate one by logging into Parseur, visiting Settings > API, and copying the key shown. 4. Paste the key into Switchy and click Authorize. 5. Return to any Space and type '@Parseur list mailboxes' to confirm the connection works — you should see a list of your active mailboxes. 6. To invoke other tools, @mention Parseur followed by the action, for example '@Parseur list documents in mailbox <mailbox_id>' or '@Parseur create webhook for mailbox <mailbox_id> to <url>'. Each command returns results inline, so the team can see parsed data or webhook status without leaving the conversation.
What teammates see: by default, memories from Parseur are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List All Mailboxes
@Parseur list all mailboxes in my account, showing the name and ID of each one.Open in a Space →
Show Recent Documents
@Parseur list the 10 most recent documents in mailbox <mailbox_id>, including their parsed fields and timestamps.Open in a Space →
Inspect Webhook Config
@Parseur show all webhooks configured for mailbox <mailbox_id>, including their URLs and current status.Open in a Space →
Pause a Webhook
@Parseur pause webhook <webhook_id> for mailbox <mailbox_id> so it stops sending parsed data until I re-enable it.Open in a Space →
Create New Webhook
@Parseur create a webhook for mailbox <mailbox_id> that posts parsed data to https://example.com/endpoint whenever a new document is processed.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Parseur list all mailboxes and show me which ones have active templates configured
Found 4 mailboxes in your Parseur account. Two have active templates: 'Customer Support Emails' (3 templates for ticket parsing) and 'Invoice Processing' (2 templates for extracting line items and totals). The other mailboxes ('Newsletter Archive', 'HR Documents') have no templates configured yet. Each mailbox ID and template count is included for reference.
This example demonstrates read-only discovery across your Parseur setup. Useful for auditing which mailboxes are production-ready versus still in configuration. Requires API key with read access to mailboxes and templates. No side effects.
@Parseur create a webhook for the 'Invoice Processing' mailbox that posts to https://api.myapp.com/invoices/ingest whenever a document is parsed
Webhook created successfully for mailbox 'Invoice Processing'. It will POST parsed data to https://api.myapp.com/invoices/ingest in real time as documents arrive. The webhook is active immediately with ID whk_abc123. You can pause or delete it later if needed. Confirm your endpoint is ready to receive POST requests with Parseur's JSON payload structure.
This write action configures real-time data flow from Parseur to your system. The webhook fires on every parsed document, so ensure your endpoint handles volume and validates payloads. Requires API key with write permissions. Side effect: live HTTP POSTs begin immediately.
@Parseur show me the last 10 documents in 'Customer Support Emails' and summarize any patterns in sender domains or subject lines
Retrieved 10 recent documents from 'Customer Support Emails'. Seven originated from @customerdomain.com, two from @partnerdomain.com, and one from a Gmail address. Subject lines cluster around 'Refund Request' (4 instances) and 'Account Access Issue' (3 instances). This suggests refund workflows and login problems are your top support drivers this week. Document IDs and timestamps are available for deeper inspection.
This synthesis example pairs Parseur's document listing with AI reasoning to surface trends. Helpful for spotting recurring issues without manual review. The pattern analysis is illustrative—actual insights depend on your mailbox's document volume and diversity. Read-only, no side effects.
Use-case deep-dives
When Parseur beats manual PDF extraction for distributed finance teams
A 3-person bookkeeping firm handles invoices from 40 clients, each sending PDFs via email in different formats. Parseur's mailbox-per-client model and template system let them route parsed line items straight to QuickBooks without opening attachments. The webhook tools mean they can pause ingestion during month-end close, then re-enable after reconciliation. This works if invoice volume stays under 500/month per mailbox and formats are stable enough to template once. Beyond that threshold, you're fighting template drift and webhook failures. If your clients send invoices in consistent formats and you need extraction without hiring a dev, Parseur is the right call.
How Parseur feeds structured data into Linear from customer emails
A 6-person support team at a B2B SaaS company receives bug reports via a shared inbox, but half the details (browser version, account tier, repro steps) are buried in prose. They set up a Parseur mailbox with a template that extracts those fields, then webhook the structured payload to Linear's API to pre-fill ticket custom fields. The list-documents tool lets them audit parsing accuracy during the first week. This setup wins if your support volume is under 200 emails/day and the report format is semi-predictable. If customers send screenshots or multi-threaded replies, Parseur's text-only parsing leaves gaps. For teams tired of copy-pasting email bodies into ticket forms, this MCP closes the loop in under an hour.
When Parseur routes inbound partnership emails into CRM records
A 10-person partnerships team at a marketplace gets 30-50 cold inquiries per week via a partnerships@ alias. Each email includes company name, revenue range, and integration ask, but in freeform prose. They use Parseur to extract those fields into a template, then webhook the JSON to HubSpot to auto-create contact records with lead source tagged. The enable/pause webhook tools let them toggle ingestion during conference season when volume spikes. This works if inquiry emails follow a rough pattern (signature blocks, consistent phrasing) and you're okay with 85-90% extraction accuracy. If inquiries are one-liners or heavily varied, you'll spend more time fixing bad parses than the MCP saves. For teams drowning in partnership inbox triage, Parseur turns email into structured pipeline in one afternoon.
Frequently asked
What does the Parseur MCP do in Switchy?
It connects your Parseur mailboxes so AI agents can list documents, manage webhooks, and inspect parsing templates without leaving the chat. You can create or pause webhooks to route parsed data, browse mailbox contents, and check which templates are available—all through natural-language prompts instead of the Parseur dashboard.
Do I need admin access to connect Parseur?
You need a Parseur API key with read and write permissions. Generate one in your Parseur account settings, then paste it into Switchy's connection flow. The key grants access to all mailboxes under that account, so use a dedicated service key if you want to limit scope later.
Can the Parseur MCP actually parse new documents?
No. Parsing happens inside Parseur when emails or files arrive. The MCP reads the results—listing parsed documents, checking templates, managing webhooks—but it doesn't trigger or configure parsing rules. If you need to adjust extraction logic, you still do that in the Parseur UI.
Why use this instead of Parseur's webhooks directly?
Webhooks push data to a fixed endpoint; the MCP pulls data on demand during a conversation. Use webhooks when you want real-time delivery to Zapier or your database. Use the MCP when an agent needs to search past documents, inspect webhook status, or create a new webhook mid-workflow without context-switching.
Who on the team should connect Parseur to Switchy?
Whoever owns the Parseur account and can generate API keys. Once connected, any Switchy workspace member can ask agents to list documents or manage webhooks. If multiple people need separate mailbox access, consider creating a shared Parseur sub-account with its own key to avoid credential sprawl.