Snov.io MCP connector
Connect Snov.io to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot, or any MCP client can find prospects, look up work emails, and research companies and LinkedIn profiles, with every search logged under the person who ran it.
- App credentials
- Free 14-day trial
- No credit card
Find the head of sales at acme.com and their work email
Working in Snov.io with Elaichi
-
Get single Snov.io domain search by ID
-
Get single Snov.io domain prospect search by ID
-
Get single Snov.io domain prospect email search by ID
How to connect Snov.io to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Snov.io MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Snov.io MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Snov.io MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Snov.io MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Snov.io MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Snov.io to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Snov.io through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Snov.io is logged.
-
Sales
Find the right contact before the first call
Ask for the people at a target company's domain and get names, titles, and work emails from Snov.io without leaving the chat.
-
Outbound
Build a prospect list from one domain
Paste a company domain and have the agent run a Snov.io domain search, then pull the prospects and their emails into a list ready for a sequence.
-
Marketing
Turn a LinkedIn profile into a contact
Drop in a LinkedIn URL and get the person's profile and work email from Snov.io for an event follow-up or a newsletter list.
-
Recruiting
Reach candidates at their work address
Search the Snov.io database for people by title and company, then find a work email to open a conversation with a passive candidate.
-
Partnerships
Research a company before you reach out
Look up a company in the Snov.io database to see its domain and the right people to contact about a partnership, then draft the note in the same chat.
-
Revenue operations
Check how many emails a domain holds
Before planning a campaign, ask how many addresses Snov.io has for a domain and review the email finder searches your team has already run.
Try asking
- “Find the head of sales at acme.com and their work email”
- “List prospects at stripe.com with marketing titles”
- “Pull the profile for this LinkedIn URL and find a work email”
What connecting Snov.io gets you
6 screens from Elaichi, each doing one job for your Snov.io account.
Ask Elaichi to work across your apps.
Find the head of sales at acme.com and their work email
List prospects at stripe.com with marketing titles
Pull the profile for this LinkedIn URL and find a work email
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask for prospects in plain language.
Ask who works at a domain and get names and emails from Snov.io.
Copy the endpoint
AI apps
One endpoint for every client you use.
Use Snov.io from Claude, ChatGPT, or Cursor with no SDK and no shared API key.
Tool catalog
48 Snov.io tools, no custom code.
Domain searches, prospect lookups, email finder, and LinkedIn profiles, ready the moment you connect.
Toolboxes
Every team gets its own Snov.io toolbox.
Scope Snov.io searches to Sales, Outbound, Recruiting, or Marketing with one toolbox each.
Shared connections
Share one Snov.io account, never the credentials.
Teammates run searches through a shared connection without ever seeing the Snov.io secret.
Audit log
Every Snov.io search names who ran it.
When, who, what happened, type, and resource, for every prospect lookup, in one log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Snov.io digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch prospects
Snov.io
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Snov.io
Queued
Workflows
A schedule starts prospecting, a person approves.
Fetch new Snov.io prospects, group them, draft a digest, approve it, post it back.
Snov.io health
Refreshed 4 minutes ago · every 15 minutes · from the prospects collection
Prospects
1,284 ↓ 12%
Emails
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Prospects created
Last 14 days
By team
Share of activity
Sales EMEA 34%
Sales US 27%
Outbound 21%
Marketing 18%
Collections and dashboards
Snov.io health, computed with no model involved.
Searches run, emails found, and records by team, refreshed on a schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Snov.io
All three can connect Snov.io to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Snov.io tools | Allow or restrict single Snov.io tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Snov.io call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Snov.io tools for your AI agents
48 tools are ready to call through Elaichi's MCP endpoint the moment you connect Snov.io, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Snov.io to Claude?
Connect Snov.io in Elaichi first by pasting the app credentials from your Snov.io account into the connection form. There is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Snov.io searches are available in the chat.
Does Snov.io work with ChatGPT and Cursor as well as Claude?
Yes. Once Snov.io is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent. You connect Snov.io once and every client picks it up.
What can an AI agent actually do with my Snov.io data?
It can search a company domain for prospects and their work emails, find an email for a named person, look up a company in the Snov.io database, and pull a profile from a LinkedIn URL. It can also check how many emails Snov.io holds for a domain and review searches your team has already run. Short concrete asks, like a name plus a domain, work better than long sentences.
Does connecting Snov.io give the AI my whole account and all my credits?
No. Every Snov.io search runs as the person who signed in to Elaichi, so the agent sees only what that person's Snov.io account can see and spends only that account's credits. Elaichi can narrow that access further with roles and restrictions, and it can never widen it beyond what Snov.io already allows.
Can I stop an agent from running costly searches in Snov.io?
Yes. Restrictions in Elaichi work per action, so you can restrict starting new Snov.io domain or database searches for a role or for one person while leaving lookups of past searches open. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to a Snov.io connection when someone leaves?
Offboarding that person in Elaichi ends their access to Snov.io through every client at once. If the Snov.io connection was shared, it keeps working for everyone else on the team. If you want it gone entirely, disconnecting Snov.io once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client.
Does the Snov.io MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Snov.io is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Snov.io?
Yes. Both let Claude, ChatGPT or Cursor use Snov.io. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Snov.io call.
How is Elaichi different from Composio for Snov.io?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Snov.io: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Snov.io in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot