Connect Snov.io to Microsoft Copilot via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Snov.io, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

Snov.io + Microsoft Copilot

Drive Snov.io lead enrichment and outreach from your AI: find a person's email from name and company domain, verify emails, list the emails of a domain, manage prospect lists and see drip campaigns and the credit balance. Signs in with the API client ID and secret.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

SNOV_CLIENT_ID, SNOV_CLIENT_SECRET

Step 1 — Get credentials

Setting up takes about 2 minutes. You need a Snov.io account with API access: the API is fully available on the paid plans, and on the free plan Snov.io gives test access on request ([email protected]).

1. Sign in to Snov.io and open Account settings → API (app.snov.io/account/api).
2. Copy the API User ID into SNOV_CLIENT_ID.
3. Copy the API Secret into SNOV_CLIENT_SECRET. Paste both without spaces.
4. Install the connector and run snov_balance: it is free and shows your remaining credits, the days until the monthly limit resets and the days until the subscription ends.

No token to paste: the connector exchanges the User ID and the Secret for an access token by itself and gets a new one every hour. There is nothing to renew by hand.

What it reads: your credit balance; how many emails Snov.io knows for a company domain; the emails found by a domain search; your prospect lists with their number of contacts; and your drip campaigns with the prospect list they use, their status (Active, Paused, Draft) and their dates.

What costs credits: snov_balance, snov_get_domain_emails_count, the domain search results, the prospect lists and the campaigns are free. snov_email_finder (first name, last name and company domain), snov_email_finder_by_url (a LinkedIn profile URL), snov_email_verifier and snov_domain_search spend credits. The AI checks the balance before bulk work and does not repeat a search that already returned results.

Domain search in two steps: the AI first asks for free how many emails a domain has, then starts the search with snov_domain_search, which costs 1 credit per unique request. snov_get_domain_search_result then returns up to 50 emails per page; while the search is still running, the AI waits a few seconds and asks again. Emails found this way are not verified: snov_email_verifier checks one address at a time and tells you whether it is valid, invalid, catch-all, disposable or webmail, with the SMTP and MX checks.

A typical run: count the emails of a domain, search the domain or find one person by name, verify the address, add the prospect to a list, and see which drip campaign uses that list.

Asks before every change: snov_create_prospect_list creates a new, empty list and snov_add_prospect_to_list adds a person to a list with email, name, job title, company, country and custom fields. Both change your Snov.io account, so the AI shows you the list and the prospect and waits for your yes.

Switched off at install: nothing, all 11 tools are on, and none of them deletes anything.

Limits: Snov.io allows 60 requests a minute, so the AI works through a long list at a steady pace instead of sending everything at once.

Common errors: 401 means Snov.io did not issue a token: the API User ID or the API Secret is wrong. A 403 "you dont have permissions for this action" on every call means your plan does not include API access.

The connector does not edit the content of drip campaigns, use the LinkedIn extension, manage sender accounts, set up webhooks or work with deals in the Snov.io CRM.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Microsoft Copilot

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.

1. In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
2. Enter a Server name (for example AnythingMCP), a Server description that says what the connector does, and the Server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server.
3. Under authentication, choose API key, set Type to Header and the header name to X-API-Key, then select Create.
4. In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
5. Try it in the agent's Test pane: ask for something that needs the Snov.io tools.
6. Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.

Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.

Available tools

Example prompts

• "How many Snov.io credits do I have left, and when does my monthly limit reset?"
• "Find the email of Julia Becker at acme-logistics.com, verify it and add her to my list Logistics Leads. Ask me before you add her."
• "How many emails does Snov.io know for hubspot.com? If there are more than 20, run a domain search and show me the first page."
• "Find the work email behind linkedin.com/in/marco-rossi-sales and tell me whether it is valid."
• "Which of my drip campaigns are active right now, and which prospect list does each one use?"

FAQ

Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.

What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.

The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT
• Connect to Cursor
• Connect to Gemini
• Connect to Meta Muse