SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Parseur MCP with Claude Agent SDK

Connect Claude Agent SDK to Parseur MCP. List all documents in your invoices mailbox, create a webhook to send parsed receipts, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Parseur logoParseur
Api Key

Parseur is an AI-powered data extraction platform that parses emails, PDFs, and documents into structured data. Automate tedious data entry and get actionable information, fast.

26 Tools

Introduction

This guide walks you through connecting Parseur to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Parseur agent that can create and manage mailboxes, upload email documents for parsing, fetch parsed results, reprocess documents, and configure webhooks through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Parseur account through Composio's Parseur MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Parseur with

Claude CodeClaude CoworkOpenAI Agents SDKCodexOpenClawHermesAtomic AgentGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAIPydantic AIAutoGen

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Parseur
  • Configure an AI agent that can use Parseur as a tool
  • Run a live chat session where you can ask the agent to perform Parseur operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

What is the Parseur MCP server, and what's possible with it?

The Parseur MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Parseur account. It provides structured and secure access to your Parseur data extraction workflows, so your agent can perform actions like managing mailboxes, handling documents, configuring webhooks, and automating template operations on your behalf.

  • Mailbox management and discovery: Let your agent list, browse, and filter all Parseur mailboxes to keep tabs on your parsing operations and document streams.
  • Document listing and retrieval: Effortlessly fetch documents from specific mailboxes, enabling automated sorting, searching, or pagination of your parsed files.
  • Template and parsing rule automation: Ask your agent to list templates within any mailbox, so you can quickly inspect or update parsing rules as your data extraction needs evolve.
  • Webhook configuration and control: Enable your agent to create, update, pause, enable, or delete webhooks, making it easy to automate real-time data delivery to your other systems.
  • Comprehensive webhook inspection: Retrieve detailed webhook information or list all webhooks for a mailbox, ensuring you always know how and where your parsed data is flowing.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Parseur account
  • Some knowledge of Python
2

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • @composio/core provides Composio integration for Anthropic
  • @anthropic-ai/claude-agent-sdk is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude
5

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The dotenv.config() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Parseur functionality
6

Create a Composio instance and Tool Router session

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });

  // Create Tool Router session for Parseur
  const session = await composio.create(USER_ID, {
    toolkits: ['parseur'],
  });
  const mcpUrl = session?.mcp.url;
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Parseur
  • The returned url is the MCP server URL that your agent will use
7

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to Parseur tools via Composio.',
  maxTurns: 10,
};
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Parseur
  • maxTurns: 10 limits the conversation length to prevent excessive API usage
8

Create client and start chat loop

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}
What's happening:
  • The readline interface is created to handle user input and output
  • The query function is used to send the user's input to the agent
  • The chat loop continues until the user types 'exit' or 'quit'
9

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
What's happening:
  • The chat function is the entry point for the application
  • The try-catch block is used to handle any errors that occur

Complete Code

Here's the complete code to get you started with Parseur and Claude Agent SDK:

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['parseur']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to Parseur tools via Composio.',
    maxTurns: 10,
  };

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Parseur through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
TOOLS

Supported Tools

Every Parseur action and event your agent gets out of the box.

Copy Document

Tool to copy a document to another mailbox.

Copy Mailbox

Tool to copy a mailbox (parser) in Parseur.

Create custom download

Tool to create a custom download (export configuration) for a mailbox.

Create mailbox

Tool to create a new mailbox (parser) in Parseur.

Delete custom download

Tool to delete a custom download (export configuration) from a mailbox.

Delete document

Tool to delete a specific document by ID.

Delete mailbox

Tool to delete a mailbox (parser) by ID.

Delete webhook

Tool to delete a specific webhook.

Disable webhook

Tool to disable a webhook for a mailbox.

Enable webhook

Enables a paused webhook for a specified mailbox, allowing it to receive and forward parsed document events.

Get Bootstrap Config

Tool to retrieve bootstrap configuration data.

Get Document

Tool to retrieve full details of a specific document by ID.

Get Document Logs

Tool to get document logs for a specific document.

Get Mailbox by ID

Tool to retrieve full mailbox (parser) configuration by ID.

Get Mailbox Schema

Tool to retrieve the JSON schema for a mailbox's parsed fields.

List Custom Downloads

Retrieve custom downloads (export configurations) and their download URLs for a mailbox.

List Documents in Mailbox

Tool to list documents within a specific mailbox.

List Mailboxes (Full Details)

List mailboxes with pagination, document counts, processing statistics, and configuration details such as field settings, processing options, and webhooks.

List Templates for Mailbox

Tool to list all templates in a given mailbox.

Reprocess a document

Tool to reprocess a document.

Retrieve a webhook

Tool to retrieve details of a specific webhook.

Skip a document

Tool to skip a document.

Update custom download

Update a mailbox's custom download configuration, including its name, field list, or export type.

Update Mailbox

Tool to update a mailbox (parser) configuration.

Update webhook

Tool to update an existing webhook’s settings.

Upload Email Document

Tool to upload an email or text document to Parseur for parsing.

FRAMEWORKS

How to build Parseur MCP Agent with another framework

Claude Code logo

Claude Code

Use Parseur MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Parseur MCP with Claude Cowork

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Parseur MCP with OpenAI Agents SDK

Codex logo

Codex

Use Parseur MCP with Codex

OpenClaw logo

OpenClaw

Use Parseur MCP with OpenClaw

Hermes logo

Hermes

Use Parseur MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Parseur MCP with Atomic Agent

Google ADK logo

Google ADK

Use Parseur MCP with Google ADK

LangChain logo

LangChain

Use Parseur MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Parseur MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Parseur MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Parseur MCP with LlamaIndex

CrewAI logo

CrewAI

Use Parseur MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Parseur MCP with Pydantic AI

AutoGen logo

AutoGen

Use Parseur MCP with AutoGen

FAQ

Frequently asked questions

With a standalone Parseur MCP server, the agents and LLMs can only access a fixed set of Parseur tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Parseur and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Agent SDK fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Parseur tools.

Yes, absolutely. You can configure which Parseur scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Parseur data and credentials are handled as safely as possible.

Start with Parseur.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Parseur tool your agent needs.Free to start.

Start building