Set up Claude and MCP servers for sales
The HotHawk MCP server hands Claude your cold email workspace, so it can build a campaign, add leads and work through replies from a chat. Here are the two ways to connect it: the connector in Claude Desktop or the web app, and one command in Claude Code. Neither runs anything on your machine.
No credit card required.
MCP https://api.hothawk.ai/mcp
An MCP server is how Claude reaches outside the chat and does real work in another tool. The HotHawk server exposes your workspace over the Model Context Protocol, so a prompt like "launch a campaign to my new SaaS leads" becomes real actions in the app, each one a tool call you can see.
As of July 2026 the exact menus move most months, so if a button has shifted since this was written, the shape below still holds: a hosted HTTP server, plus a one-time OAuth sign-in. Everything after that is just talking to Claude.
Route 1
Claude Desktop or the web app
This is the point-and-click route. No terminal, about two minutes. It is the same flow whether you are on Claude Desktop or the web app.
-
1
Open your settings
In Claude, open Settings and find the Connectors section.
-
2
Add a custom connector
Click Add Custom Connector, then fill in the fields below and click Add.
NameHotHawkRemote MCP Server URLhttps://api.hothawk.ai/mcpOAuth Client ID Advanced settingshothawkOAuth Client Secret Advanced settingshothawk -
3
Authorise access
Claude sends you to a HotHawk authorisation page. Click Allow and wait for it to finish. If you are not logged in you will sign in first, then come back automatically. Do not close the page until it returns you to Claude.
-
4
Ask for something
Access is at the account level, so tell Claude which workspace to work in. A good first prompt:
Try asking"What workspaces do I have, and which have unread positive replies?"
Want the screen-by-screen version with the connector popup shown? The full walkthrough lives on the MCP server page.
Route 2
Claude Code, from the terminal
If you live in VS Code or a terminal, Claude Code adds the server with one command. Because HotHawk is a remote HTTP server, you pass the transport and the URL, then sign in.
claude mcp add --transport http hothawk https://api.hothawk.ai/mcp
Claude Code flags the server as needing sign-in the first time it gets a 401 or 403 back. Open the MCP panel to finish the OAuth flow, click Allow on the HotHawk page, and you are connected.
# inside Claude Code, open the MCP panel and finish the OAuth sign-in
/mcp
Check it stuck, and use the same /mcp
panel any time to reconnect or remove it:
claude mcp list
# hothawk https://api.hothawk.ai/mcp ✓ connected
There is a short form too, if you type this a lot. -t
is --transport,
and -H
is --header for servers that take a token instead:
# -t is short for --transport
claude mcp add -t http hothawk https://api.hothawk.ai/mcp
The bit everyone gets stuck on
Do I need Python or Node for this?
No. That instruction comes from a different kind of MCP server. Guides tell you to install Python or Node when the server is a local one, running as a program on your own machine over stdio. The runtime is for the program, not the protocol.
HotHawk is a hosted server. It runs on our side at https://api.hothawk.ai/mcp
and Claude reaches it over HTTP. There is no local process to start, no dependency to install, and
nothing that stops working when you close your laptop. You add the URL and authorise once.
The two commands side by side make the difference obvious:
# A LOCAL (stdio) server: this one DOES need Node on your machine.
claude mcp add my-local-tool -- npx -y some-local-mcp-server
# HotHawk is HOSTED over HTTP: nothing to install, you just sign in.
claude mcp add --transport http hothawk https://api.hothawk.ai/mcp
Only the first line ever needs a runtime, because it spawns a program with npx.
The HotHawk line spawns nothing.
MCP setup FAQs
Do I need to write any code to set this up?
No. In Claude Desktop or the web app you add HotHawk as a custom connector through the settings menu, no terminal involved. In Claude Code it is a single command, then you sign in. Building against the REST API is there if you want it, but connecting the MCP server is not a coding job.
Which Claude apps can use the HotHawk MCP server?
Claude Desktop and Claude Code both connect cleanly. Custom connector support on the claude.ai web app depends on your plan and is still rolling out through 2026, so if you cannot see the option there, use Claude Desktop or Claude Code instead. The server itself is the same hosted endpoint whichever app you point at it.
Is it secure?
You authorise access through Claude's own OAuth flow and you can revoke it at any time from your HotHawk account. Access is granted at the account level, and you tell Claude which workspace to act in, so nothing runs without your say-so. HotHawk never sees your Claude conversation, and Claude never sees your password.
What is the difference between a local and a hosted MCP server?
A local (stdio) server is a program you run on your own machine, which is why those setups ask you to install Python or Node first. A hosted server runs on the vendor's side and you reach it over HTTP. HotHawk is hosted, at https://api.hothawk.ai/mcp, so there is no runtime to install and nothing to keep running. You add the URL and sign in.
Can ChatGPT or another assistant use it?
The HotHawk MCP server is built around Claude's connector and OAuth flow, so Claude is where it fits best today. If you want to wire HotHawk into ChatGPT, a custom agent or your own code, use the HotHawk REST API instead: Bearer auth, the same actions, and webhooks for replies.
Send cold emails that get delivered. Never miss a positive reply.
Serious deliverability paired with the best reply management in the market.
No credit card required.