Warm.Deals Developers

Warm.Deals in your AI assistant

Warm.Deals runs a remote Model Context Protocol server. Connect it to ChatGPT, Claude, Codex, Cursor, VS Code or Gemini CLI and your assistant can find B2B companies, keep them in your CRM, draft outreach and report on results — in your own workspace, with your permissions.

Server URL

url
https://warm.deals/mcp

Streamable HTTP transport. Sign-in is OAuth 2.1 with PKCE — your assistant opens a Warm.Deals page where you pick the workspace and choose full or read-only access. No API key to copy. A free Warm.Deals account works; plan limits apply exactly as in the app.

Connect

Claude (web, desktop, mobile)

Settings → Connectors → Add custom connector → paste the server URL, or open the prefilled form. Then click Connect and sign in.

ChatGPT

Until the Warm.Deals plugin is listed in the ChatGPT directory: Settings → Apps → Advanced → Developer mode, then Create app → paste the server URL → OAuth → Create, and sign in.

Claude Code

bash
claude mcp add --transport http warmdeals https://warm.deals/mcp
# then run /mcp inside Claude Code and choose "Authenticate"

Codex

toml
# ~/.codex/config.toml
[mcp_servers.warmdeals]
url = "https://warm.deals/mcp"

# then: codex mcp login warmdeals

Cursor, VS Code, Windsurf and other MCP clients

json
{
  "mcpServers": {
    "warmdeals": { "url": "https://warm.deals/mcp" }
  }
}

Gemini CLI and clients without OAuth

Clients that cannot run an OAuth sign-in can send a workspace API key instead (Settings → API keys; a Read-only key keeps the assistant from changing anything).

bash
gemini mcp add --transport http warmdeals https://warm.deals/mcp \
  --header "Authorization: Bearer lf_your_key_here"

Try asking

  • Find 30 dental clinics in Warsaw with an email address and save them to my Warm.Deals CRM.
  • Which deals in my pipeline haven't moved in two weeks? Draft a follow-up for each.
  • Write a short cold email for Acme GmbH about our bookkeeping service, but don't send it.
  • How did last month's outreach perform — opens, replies and meetings?
  • Run the pre-send check on my 'Q4 clinics' campaign and explain every warning.

What the assistant can do

Prospecting

  • find_leads — companies of a kind in a place, returned in one call
  • start / get / preview / save lead search — the same search step by step
  • find_contacts, find_email — decision makers and work emails for a lead
  • enrich_lead, research_prospect, technographics, hiring_signal
  • similar_profile, icp_match, semantic_search

CRM

  • search_leads, get_lead, create_lead, update_lead, lead_activity
  • list_contacts, create_contact, list_accounts, list_segments, preview_segment
  • list_deals, create_deal, update_deal, move_deal, pipeline_stats, revenue_forecast
  • list_tasks, create_task, complete_task
  • export_leads, get_export_status

Outreach & inbox

  • compose_message, generate_icebreaker, ask_copilot, search_sales_kb
  • list_campaigns, get_campaign, create_campaign, campaign_preflight
  • launch_campaign, pause_campaign, enroll_in_sequence (these send real messages — the assistant asks first)
  • list_inbox_threads, get_inbox_thread, suggest_reply, reply_thread

Analytics

  • analytics_summary, email_funnel, deal_funnel, leads_timeline
  • sequence_stats, send_time_recommendations, generate_report

Every tool is annotated read-only or destructive, so your assistant asks before anything that changes data or sends a message. Deleting records, managing users, connecting mailboxes and changing workspace settings are not available to assistants at all — those stay in the app. Search results come from public business data: OpenStreetMap, open company registries and companies' own public websites.

Permissions, data and revoking access

  • A connection acts as you, inside the one workspace you chose, and never beyond your own role.
  • Read-only connections can look but not change anything. Access tokens live one hour and are refreshed automatically; refresh tokens rotate on every use.
  • See and disconnect every connected assistant under Settings → API keys & MCP.
  • Data handling is described in our Privacy Policy, DPA and sub-processor list.

Support

Questions or problems connecting: support@warm.deals. Technical details: OAuth metadata at /.well-known/oauth-authorization-server, protected-resource metadata at /.well-known/oauth-protected-resource/mcp.