How to integrate Icypeas MCP with Claude Code

Framework Integration Gradient
Icypeas Logo
Claude Code Logo
divider

Introduction

Manage your Icypeas directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Rube - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Why Rube?

Rube is a universal MCP server with access to 850+ SaaS apps. It ensures just-in-time tool loading so Claude can access the tools it needs, a remote workbench for programmatic tool calling and handling large tool responses out of the LLM context window, ensuring the LLM context window remains clean.

Connect Icypeas to Claude Code with Rube

1. Get the MCP URL

Copy and paste the below command in Claude Code to add Rube MCP.

Terminal

2. Authenticate Rube

Run /mcp to view Rube

bash
/mcp
Run /mcp to view Rube in Claude Code
Click on Rube to authenticate
Authentication flow complete

3. Ensure it's connected

Run /mcp again to verify the connection. Now, do whatever you want with Claude Code and Icypeas.

Rube connected successfully

Supported Tools & Triggers

Tools
Bulk Email SearchTool to start a bulk email search job.
Check Search ProgressTool to check the progress of a search by its ID.
Domain ScanTool to scan a domain for role-based email addresses.
Fetch Bulk Search InfoTool to fetch information about bulk search files.
Fetch Subscription InformationTool to fetch subscription and credit info.
Find CompaniesTool to search companies in Icypeas database.
Find Company URLTool to find a single company profile URL using a company name or domain.
Find PeopleTool to search for people in the leads database.
Find Profile URLTool to find a single profile URL.
Find Profile URLs BulkTool to perform bulk search for profile URLs.
Find Single EmailTool to discover a single email address using a person's first or last name with a company domain or name.
Retrieve Search ResultsTool to retrieve the results of a search by ID or to paginate through bulk search results.
Scrape CompanyTool to scrape company profile information from a LinkedIn company URL.
Scrape ProfileTool to initiate scraping of a LinkedIn profile.
Setup NotificationsTool to set up push notifications.
Statistics Bulk SearchTool to parse bulk search statistics webhook.

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

The Icypeas MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Icypeas account. It provides structured and secure access to professional email discovery and verification, so your agent can perform actions like finding emails, verifying addresses, searching company data, and scanning domains on your behalf.

  • Accurate email discovery and verification: Instantly find and verify professional email addresses using first name, last name, and company domain to supercharge your outreach or lead generation.
  • Bulk prospecting and search management: Launch bulk email or profile URL searches for thousands of contacts at once, then track progress and fetch results without manual oversight.
  • Comprehensive company and people lookup: Search for companies or filter people by name, title, company, and more to enrich your CRM or build targeted prospect lists efficiently.
  • Domain scanning for role-based emails: Scan entire company domains to discover all available role-based email addresses, simplifying large-scale contact discovery.
  • Subscription and usage insights: Check your Icypeas subscription details and remaining credits, helping you stay on top of your usage and plan outreach campaigns smarter.

Connecting Icypeas via Tool Router

Tool Router is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Icypeas) for even more tool search precision. It's secure and reliable.

How the Tool Router works

The Tool Router 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

Prerequisites

Before starting, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Icypeas account
  • Basic knowledge of Python or TypeScript

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)

Install Composio library

pip install composio-core python-dotenv

Install the Composio Python library to create MCP sessions.

  • composio-core provides the core Composio functionality
  • python-dotenv loads environment variables from your .env file

Generate Composio MCP URL

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["icypeas"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http icypeas-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Create a script to generate a Composio MCP URL for Icypeas. This URL will be used to connect Claude Code to Icypeas.

What's happening:

  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Icypeas
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it

Run the script and copy the MCP URL

python generate_mcp_url.py

Run your Python script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output

Add Icypeas MCP to Claude Code

bash
claude mcp add --transport http icypeas-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (icypeas-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

Verify the installation

bash
claude mcp list

Check that your Icypeas MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your icypeas-composio entry in the list
  • This confirms that Claude Code can now access Icypeas tools

If everything is wired up, you should see your icypeas-composio entry listed:

Claude Code MCP list showing the toolkit MCP server

Authenticate Icypeas

The first time you try to use Icypeas tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Icypeas
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Icypeas authorization flow
  • Return to the terminal and start using Icypeas through Claude Code

Once authenticated, you can ask Claude Code to perform Icypeas operations in natural language. For example:

  • "Find verified email for John Doe at acme.com"
  • "Bulk search emails for 100 new leads"
  • "List all role-based emails at example.org"

Complete Code

Here's the complete code to get you started with Icypeas and Claude Code:

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["icypeas"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http icypeas-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Conclusion

You've successfully integrated Icypeas with Claude Code using Composio's MCP server. Now you can interact with Icypeas directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Icypeas operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Icypeas operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

How to build Icypeas MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Icypeas MCP?

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

Can I use Tool Router MCP with Claude Code?

Yes, you can. Claude Code 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 Icypeas tools.

Can I manage the permissions and scopes for Icypeas while using Tool Router?

Yes, absolutely. You can configure which Icypeas 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.

How safe is my data with Composio Tool Router?

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 Icypeas data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.