Connect a client
Setup for Claude, Cursor, VS Code, ChatGPT, Codex, Gemini CLI and more.
Tool reference
All 16 tools, their arguments and what they do.
Authentication
Sign in with your browser, or use an API key.
Recipes
Complete conversations that go from ICP to launched campaign.
What it can do
How it is built
Three properties are worth knowing before you connect it to anything.The server holds no secrets
The server holds no secrets
Every request carries your credential as
Authorization: Bearer …, and
each tool forwards it to the ManyPI REST API. The MCP server itself stores
nothing — no keys, no tokens, no data. Authorization, rate limiting and
credit accounting all happen in the ManyPI API, exactly as they do for a
direct REST call.One credential = one workspace
One credential = one workspace
Whichever credential you connect determines which ManyPI workspace the tools
act on. To work across brands, switch brand in ManyPI, or pass brand-aware
parameters where the underlying endpoint supports them.
It is stateless
It is stateless
A fresh server and transport are built per request, so many users with
different credentials are served concurrently and safely. There is no
session to expire and nothing to reconnect.
Tools are annotated for safety
Every tool declares whether it reads, writes, or does something irreversible. MCP clients use those hints to decide what to run automatically and what to ask you about first.draft_email is annotated read-only despite being a POST: it returns generated
text and persists nothing. No sequence is saved, no email is sent.
Requirements
- A ManyPI account. Lead generation, validation and scraping work on the free plan; sending requires a paid plan.
- A client that speaks MCP over Streamable HTTP, or
mcp-remotefor stdio-only clients.
Connect your client
Copy-paste setup for every supported client.
