The MCP Server for Email Outreach
Connect Claude or any AI agent to Skyp. Create campaigns, add contacts, trigger personalized sends, and get results back with no middleware and no manual steps.
Your AI agent, connected to outreach
Model Context Protocol (MCP) is an open standard that lets AI agents interact with external tools using a shared protocol. Instead of building custom integrations, your agent connects once and gets a menu of actions it can call in natural language.
Skyp's MCP server is the only email outreach MCP that covers the full campaign lifecycle, not just querying dashboards, but actually executing outreach on behalf of your agent.
What your agent can call
create_new_campaignCreate and configure a new outreach campaign with AI prompt, tone, and targeting
add_contact_to_existing_campaignAdd an enriched contact to a running campaign: AI writes a unique email on the spot
get_campaign_detailsQuery campaign status, open rates, reply rates, and meetings booked
update_existing_campaignPause, resume, or update campaign settings programmatically
list_campaignsList all active and paused campaigns with performance metrics
create_new_contactAdd a new contact with enrichment context that informs AI personalization
get_account_analyticsPull account-wide performance data across all campaigns and all reps
get_campaign_threadsRetrieve reply threads from a campaign for agent-driven follow-up logic
How Clay, Skyp, and HubSpot work together
One workflow. Research, outreach, and CRM sync run end-to-end without a human in the loop.

Waterfalls 100+ data sources, runs AI research via Claygent, finds and qualifies the lead
Claygent → Skyp MCP: add_contact_to_existing_campaignAI writes a unique email using the enrichment context. Manages domains, warmup, and deliverability end-to-end.
Skyp webhook: reply_received → trigger CRM updateHubSpot's official MCP logs the reply, updates deal stage, and triggers the next workflow automatically
No middleware. Every step is an MCP call. One engineer runs outreach for the whole team.
Important: Clay MCP contacts are session-scoped
When you pull contacts from Clay via MCP, those contacts only exist for the duration of that Clay session. Clay does not store them for later. If you find a set of contacts in a Clay MCP session but don't pass them to Skyp immediately, you will need to run the Clay lookup again (and pay the credits again) in a future session. The workflow above works best when the full Clay-to-Skyp handoff happens in a single agent run.
Native MCP vs. community wrappers
Not all email outreach MCPs are equal. Here's how Skyp compares.
| Tool | MCP Type | Depth | AI Writing |
|---|---|---|---|
| Skyp | Native ✓ | Full lifecycle: create, send, results | Yes, per-prospect |
| Smartlead | Official ✓ | 116+ tools, infrastructure focused | No |
| Saleshandy | Official ✓ | Account & campaign access | No |
| Instantly | Community ~ | Read-heavy, basic write | No |
| Outreach | Via Workato | Middleware required, paid add-on | No |
| Unify GTM | None ✗ | OpenAI-only, no open protocol | Proprietary only |
MCP access included from day one
MCP is not an add-on. It's included with every Team, Growth, and Enterprise plan, with no middleware, no connector, and no extra cost.
See plans & pricingFrequently Asked Questions
What is Skyp's MCP server?
Which AI agents work with Skyp's MCP?
Does Skyp's MCP let agents actually send emails, or just read data?
What plans include MCP access?
How does Skyp MCP compare to other email outreach MCPs?
Does the MCP server require any infrastructure setup?
How does Clay work with Skyp MCP?
Ready to build your agentic GTM stack?
Connect Claude or any AI agent to Skyp and run personalized outreach without opening the app.
Get a Demo