add the server.
One URL, https://mcp.drippay.dev/mcp. Paste it into Claude, Cursor, ChatGPT, or any HTTP MCP client.
Connect dreach to Claude, Cursor, or ChatGPT with one URL and drive sourcing, enrichment, and drafting by just talking to your AI. The dreach app sends it on autopilot.
one url · about two minutes · no code
How it works
One URL, https://mcp.drippay.dev/mcp. Paste it into Claude, Cursor, ChatGPT, or any HTTP MCP client.
Authorize with your dreach account over OAuth, or paste a dreach secret key for headless setups.
Ask it to find leads, enrich contacts, or draft outreach. About two minutes, no code.
What you can do
Seven hosted tools, grouped into the jobs you actually run.
find leads
Tell your agent who you sell to. dreach sources matching people and companies and hands back a list you can work.
drip_find_leads
get verified contacts
Turn a list of names into reachable contacts, with verified business emails and phone numbers.
drip_get_contacts
draft personalized messages
dreach researches every lead and drafts a personalized first message, ready for your campaign to send on autopilot.
drip_draft_messages
set up sending infrastructure
Provision managed sending domains and inboxes, then poll their readiness as they warm up.
drip_provision_inboxes, drip_inbox_status
watch signals and check usage
Track executive-change monitors for warm timing, and read your account balance and credit usage.
drip_signals, drip_account
How it fits together
The hosted server does sourcing, enrichment, drafting, and provisioning. Sending, replies, inbox triage, and campaign control run in the dreach app on your machine. Put it on autopilot and outreach goes out on its own, replies included.
Connect
OAuth is the simple path: paste the URL and sign in with dreach. The secret key is for headless setups where a browser sign-in is not available.
claude mcp add --transport http drip-cloud https://mcp.drippay.dev/mcpclaude mcp add --transport http drip-cloud https://mcp.drippay.dev/mcp \
--header "Authorization: Bearer sk_live_..."Cursor and other HTTP clients
Add the server URL https://mcp.drippay.dev/mcpto your client's MCP config and sign in with dreach. Any client that speaks streamable HTTP MCP works the same way.
Security
The hosted proxy forwards authorized calls to the dreach backend; dreach owns the grant and credential records described here.
dreach stores one dedicated, scoped API key encrypted for each OAuth grant. Revoking the grant disables that key.
OAuth access and refresh tokens are stored only as hashes and are never logged in plain text.
Access is scoped to read or write, so a read-only connection cannot make changes.
The Model Context Protocol is an open standard that lets AI agents connect to tools and data. The dreach MCP server exposes your outbound tools to any MCP client so your agent can use them directly.
No. Add one URL, sign in with dreach, and ask your agent in plain language. Setup is about two minutes.
Yes. The hosted server sources, drafts, and sets up infrastructure; the dreach app on your Mac runs the campaign and sends on autopilot, replies included. Hold any thread on drafts for review if you want.
dreach stores OAuth token hashes and one encrypted, scoped API key for each grant. Revoking the grant disables that key.
Claude, Cursor, ChatGPT, and any HTTP MCP client. OAuth sign-in works where the client supports it, and a secret key covers headless setups.
For sending, replies, and inbox triage, yes. That is where campaigns run and autopilot sends. Sourcing, enrichment, and drafting all work from the hosted server on their own.
One URL to start
Add https://mcp.drippay.dev/mcp, sign in, and start sourcing.
The hosted server drafts. The dreach app sends on autopilot.