Hollerpost MCP server
Connect the AI assistant you already use to your Hollerpost workspace. The remote URL is https://mcp.hollerpost.com/mcp.
What it is
MCP (Model Context Protocol) is how AI assistants like Claude, ChatGPT and Cursor use outside tools. Our MCP server gives your assistant a set of Hollerpost tools: read your brand, add contacts who said yes, draft a campaign in one of your templates, preview it, send you a test, and report on how it did. Your assistant does the writing and the thinking. Hollerpost renders the email with your header, footer and unsubscribe link, and sends it from your own domain. Everything goes through the same Hollerpost API and the same API key, so it has the same limits and the same consent rules. It’s included on every plan, Free included.
Set up your whole account from chat
The server comes with a prompt called setup_workspace. Pick it from your assistant’s list of prompts (or just ask it to set up your Hollerpost account) and it walks through the whole thing: checks your account, adds your sending domain, hands you the DNS records, checks them, saves notes on how you like to sound, adds the first contacts you paste in (once you confirm they agreed), and drafts a welcome email. It stops before anything sends.
If your assistant also has a tool for your DNS provider (Cloudflare has one, for example), it can offer to add the records for you. Otherwise it shows them as a table you copy over. Here’s roughly how the domain part goes:
- You
Set up my Hollerpost account. I want to send from mail.sunnyside.example.
- Your assistant
You’re on the Free plan for Sunny Side Salon. I added mail.sunnyside.example. Your DNS is at Cloudflare, so add the records in this table there. I’ll check them when you say they’re in.
- You
Done.
- Your assistant
Most of them are found. One DKIM record isn’t: its name should end in
._domainkey.mail.sunnyside.example, and the one I see ends in.sunnyside.exampletwice. Cloudflare adds your domain for you, so paste only the first part. - You
Fixed it.
- Your assistant
All records found. mail.sunnyside.example is verified, so you can send from it. Next: want to tell me how you like your emails to sound?
Connect
First, make an API key in your dashboard under Settings, Developer API. Keys start with hp_live_, or uc_live_ for Utopian Creations workspaces. Either works here, and the key is shown once. Make a separate key for your AI so you can revoke it on its own.
When you create the key, the dashboard also shows a connector URL with your key already in it, and a ready-made Claude Code command. Copy the one you need before you click Done. Then pick your assistant below.
There are three ways to connect:
- Connector URL (Claude.ai, Claude Desktop connectors, ChatGPT):
https://mcp.hollerpost.com/mcp?key=hp_live_your_key_here. Your key rides in the URL, and you leave authentication empty. Nothing to install. - Header (Claude Code, Cursor):
https://mcp.hollerpost.com/mcp, with the headerAuthorization: Bearer hp_live_your_key_here. - Local:
npx -y hollerpost-mcp, with your key in theHOLLERPOST_KEYenvironment variable. Runs on your computer and needs Node.js. The package is hollerpost-mcp on npm.
Claude (claude.ai and Claude Desktop connectors)
- Go to Customize, then Connectors. Click + Add, then Add custom connector.
- Name it Hollerpost and paste your connector URL, the one with
?key=on the end:https://mcp.hollerpost.com/mcp?key=hp_live_your_key_here. - Leave the authentication and advanced settings empty: no OAuth client ID, no request headers. Click Add.
We recommend the URL over a request header here: it’s the setup we’ve tested end to end with Claude’s connectors, and it has the fewest settings to get wrong.
The URL contains your key, so treat it like a password: don’t paste it anywhere else, and revoke the key in your dashboard if it leaks. On Team and Enterprise plans, an owner has to add the connector for the organization first. Connectors you add on claude.ai also show up in the Claude desktop app.
Claude Code
Run this in your terminal. It sends the key as a header, so it stays out of the URL:
claude mcp add --transport http hollerpost https://mcp.hollerpost.com/mcp --header "Authorization: Bearer hp_live_your_key_here"
The word Bearer and the space after it matter. Run /mcp inside Claude Code to check it says connected.
Claude Desktop (local)
In Claude Desktop, open Settings from the Claude menu, go to Developer and click Edit Config. That opens claude_desktop_config.json. Add this, with your key, then quit Claude Desktop completely and open it again:
{
"mcpServers": {
"hollerpost": {
"command": "npx",
"args": ["-y", "hollerpost-mcp"],
"env": {
"HOLLERPOST_KEY": "hp_live_your_key_here"
}
}
}
}
If you already have other servers in that file, add the "hollerpost" block next to them inside "mcpServers".
Cursor
Add this to .cursor/mcp.json in your project (or ~/.cursor/mcp.json for every project). It reads your key from the HOLLERPOST_KEY environment variable, so the key stays out of the file:
{
"mcpServers": {
"hollerpost": {
"url": "https://mcp.hollerpost.com/mcp",
"headers": {
"Authorization": "Bearer ${env:HOLLERPOST_KEY}"
}
}
}
}
Rather run it locally? The same block from the Claude Desktop section works in Cursor’s mcp.json too.
ChatGPT
ChatGPT adds remote MCP servers from its Plugins page on the web. Open chatgpt.com/plugins, select the plus button, then Add custom MCP server. Give it a name, paste the remote URL under Connection, and create it as a plugin. Your account or workspace settings decide whether you can add one.
ChatGPT can’t send a custom header, so put your key in the URL instead and choose no authentication:
https://mcp.hollerpost.com/mcp?key=hp_live_your_key_here
The server never writes keys to its logs, but anyone who sees that URL can use the key, and a URL is easier to leak than a header. So make a key just for ChatGPT, leave Send unchecked unless you need it, and revoke it if you stop using it. Any other assistant that can’t send headers can use this too, or run the local npx setup instead.
If it won’t connect
- Claude.ai or Claude Desktop connector: use the URL with
?key=and remove any request header or OAuth settings. Delete the connector and add it again if you changed it. - Check the key: it starts with
hp_live_oruc_live_, has no spaces, and hasn’t been revoked. If you’re not sure, make a new key and copy the connector URL it shows you. - Header setups: the value is
Bearer, a space, then the key. - Still stuck? Email support@hollerpost.com with the time you tried and which assistant you used (never the key). We can see each connection attempt and tell you what went wrong.
Scopes
Each API key has scopes that decide what it can do. A new key starts with read, contacts, draft and account. That’s enough to set up your account and draft campaigns, and none of it can send to your list or spend money. Change them when you make the key.
| Scope | Lets the key | On by default |
|---|---|---|
read | See your workspace, brand, templates, tags, contacts, campaigns, stats and events. | Yes |
contacts | Add contacts (with consent). | Yes |
draft | Draft and edit campaigns, preview them, send tests to your team, and save brand voice notes. Also store pictures for emails, and edit your page, launch page and calendar events (publishing still needs your yes). | Yes |
send | Schedule and cancel campaigns, and send one-off emails. | No |
webhooks | Add, list and remove webhooks. | No |
account | Change your workspace name, from name, reply-to and footer address; add, check and remove sending domains; fill in, check and submit your texting registration; get a billing portal link. | Yes |
About send
It lets the key schedule campaigns to your whole list. Only turn it on for tools you trust. Without it, your assistant can draft and test as much as it likes, and you schedule the send yourself in the dashboard.
If a tool needs a scope the key doesn’t have, it gets 403 insufficient_scope and your assistant tells you which scope was missing. Nothing happens.
Tools
These are the tools your assistant sees. “Scope” is what the API key needs for that tool, and “Uses sends” means it counts toward your plan’s monthly emails.
| Tool | What it does | Scope | Uses sends | Can you undo it |
|---|---|---|---|---|
workspace_info | Who you are: workspace, plan, scopes and brand, in one call. | read | No | Read only |
brand_get | Your logo (and dark-mode logo), colors, theme, info bar, footer, social links, voice notes and sending domain. | read | No | Read only |
brand_set_voice | Saves notes on how your emails should sound. | draft | No | Yes, save new notes |
brand_set_footer | Saves the footer every email carries: link buttons, Follow us icons and a small disclaimer. | draft | No | Yes, save the old footer |
brand_set_theme | Saves the email look: colors, button style and shape, the dark-mode logo, and the info bar at the top. | draft | No | Yes, save the old look |
templates_list | Your templates and what each one needs filled in. | read | No | Read only |
segments_list | Your tags and how many subscribed people have each. | read | No | Read only |
contacts_search | Finds contacts by email, status or tag. | read | No | Read only |
contacts_add | Adds or updates one contact. Only works when the person agreed to hear from you. | contacts | No | Not from chat. Edit them in your dashboard |
email_image_upload | Stores a picture for your emails, from a public link or the file itself, and gives back its address. | draft | No | Nothing is sent. The picture stays in your image library |
email_image_upload_link | Makes a one-time page where you upload pictures from your own device. The link works once, for 30 minutes. | draft | No | Nothing is sent |
email_images_list | Pictures already stored for your emails, newest first, so they can be reused. | read | No | Read only |
campaign_draft | Makes a new draft campaign from a template, with a subject, content and audience. It can also ask one survey question that people answer with one click. | draft | No | Nothing is sent. Drafts can be edited |
campaign_update | Edits a draft, including adding or removing its survey question. | draft | No | Yes, edit it again |
campaign_preview | Shows the finished email, how many people it goes to, what that leaves of your sends, and any warnings. | draft | No | Read only |
campaign_send_test | Sends a test to up to 3 people on your workspace. | draft | Yes, one per test email | No, it’s sent |
campaign_schedule | Schedules a draft to send now or later. Needs the send scope. | send | Yes, one per person | Yes, with campaign_cancel, until it starts sending |
campaign_cancel | Cancels a scheduled campaign before it sends. | send | No | Yes, schedule it again |
campaigns_list | Lists your campaigns, by status. | read | No | Read only |
campaign_stats | Sent, delivered, bounced, opened, clicked, unsubscribed, and the top links. | read | No | Read only |
email_send | Sends one email to one person, like a receipt or a reply. Needs the send scope. | send | Yes, one | No, it’s sent |
events_recent | Recent events: signups, unsubscribes, bounces, complaints. | read | No | Read only |
surveys_list | Your surveys, their questions, response counts and the share link for open ones. | read | No | Read only |
survey_results | Totals for one survey: answer counts, average rating, recommend score and the latest written answers. No names. | read | No | Read only |
survey_create | Makes a new survey as a draft. Nobody sees it until it’s opened. | draft | No | Yes, edit or close it |
survey_update | Edits a survey, or opens or closes it. Open it before a campaign that asks one of its questions goes out. | draft | No | Yes, close or edit it |
page_get | Your page: its links, events, handle, and whether it’s published. | read | No | Read only |
page_update | Edits your page. Publishing needs your yes; until then, edits to a live page wait as a draft and the public page stays as it was. | draft | No | Yes, edit it again |
page_link_add | Adds a link to your page (up to 30). | draft | No | Yes, with page_link_remove |
page_link_update | Edits one link on your page. | draft | No | Yes, edit it again |
page_link_remove | Removes a link from your page. Asks for confirmation. | draft | No | No. Add it again |
page_links_reorder | Changes the order of the links on your page. | draft | No | Yes, reorder them again |
event_list | Your calendar events, upcoming and from the past 90 days. | read | No | Read only |
event_create | Adds a calendar event. It stays a draft unless you say to show it on your page. | draft | No | Yes, edit or cancel it |
event_update | Edits a calendar event. Changes to an event already on your page wait for your yes. | draft | No | Yes, edit it again |
event_cancel | Cancels an event and takes it off your page. Asks for confirmation. | draft | No | No. Make a new event |
launchpad_get | Your launch page: signups, confirmed people, the share link, and the saved launch note and first button. | read | No | Read only |
launchpad_update | Saves the launch page’s headline, pitch, launch note and first button as a draft. Can also build the whole page from blocks (the advanced editor). Doesn’t publish anything. | draft | No | Yes, edit it again |
launchpad_go_live | Puts your launch page live after you say yes. Automatic checks run first, and it may be held for review. Sends no email. | draft | No | Yes, switch it back to waitlist with launchpad_update |
launchpad_set_offline | Takes your launch page offline after you say yes, or puts it back. Visitors go to Your page (or hollerpost.com) while it is offline. Your signups and design stay. | draft | No | Yes, run it again with the other setting |
launchpad_domain_set | Shows your launch page at your own subdomain, like join.yourbusiness.com, after you say yes. Gives you the one DNS record to add. | draft | No | Yes, with launchpad_domain_remove |
launchpad_domain_remove | Stops showing your launch page at your own address. Your hollerpost.com address keeps working. Asks for confirmation. | draft | No | Yes, set it again with launchpad_domain_set |
account_get | Your plan, sends used this month, and billing date. | read | No | Read only |
account_update | Changes your workspace name, from name, reply-to or footer address. | account | No | Yes, change it back |
domain_add | Adds a sending domain and returns the DNS records to put in. | account | No | Yes, with domain_remove |
domain_list | Your sending domains and whether each is verified. | read | No | Read only |
domain_verify | Checks your DNS records now and says which ones are right and which are wrong. | account | No | Read only |
domain_remove | Removes a sending domain. Asks for confirmation, and won’t remove one a scheduled campaign is using. | account | No | No. Add it again and redo the DNS records |
sms_setup_status | Where your texting number’s carrier registration stands, what’s left to do, and how to fix a rejection. | read | No | Read only |
sms_registration_update | Fills in or fixes your texting registration form, while it’s a draft or after a rejection. Your business registration number is entered in the dashboard only. | account | No | Yes, change it again before you submit |
sms_website_check | Runs the carriers’ checks on your form, website, privacy policy and terms, and lists what to fix. | account | No | Nothing to undo |
sms_numbers | Toll-free numbers you can pick for texting. | account | No | Read only |
sms_registration_submit | Sends your registration to the carriers after you say yes. The first time, it also gets the toll-free number you picked (included in your add-on). Every check runs again first. | account | No | No. The carriers review it; you can fix and resubmit after a rejection |
billing_portal_link | Gives you a link to your billing page. You open it and make any changes there. | account | No | Nothing changes from chat |
Safety
The point is that an assistant can do the busy work without being able to surprise you. These rules are in the server and the API, not just in the tool descriptions:
- Preview before schedule. Your assistant is told to preview a campaign and show you the audience count and the sends it uses before it schedules anything. Scheduling needs an explicit confirmation and that audience count. If your list changed by more than 5% since the preview, the schedule is refused and your assistant gets the new count to show you.
- A person reviews your first campaign. The first campaign from a new workspace is reviewed by a person before it sends. An assistant can’t skip that; it’s told the review is pending.
- Consent to add contacts. Adding a contact requires confirming the person agreed to hear from you. Anyone who unsubscribed or bounced stays that way.
- Tests go to your team. Test sends only go to people on your workspace, never to an address the assistant picks.
- No billing changes. No tool can change your plan, buy a send pack or touch a card. The only billing tool hands back a link to your billing page, and a person opens it.
- Removals ask first.
domain_remove,page_link_removeandevent_cancelare the only tools that remove anything, and each needs confirmation. There’s no tool to delete contacts, campaigns or webhooks.
Limits
Each key can make 600 requests a minute, the same as the API. If your assistant goes over, the server waits and tries once more, then tells it to slow down.
Emails sent through the MCP server count toward your plan’s monthly sends, the same as campaigns you send from the dashboard. On Free that’s 1,000 emails a month. The MCP server itself costs nothing extra.
Stuck? Email support@hollerpost.com. It comes to me.
Sources
The setup steps above were checked against each app’s own docs. Apps move their menus now and then; if a button has moved, these pages will have the current name.
- Claude Help Center, Getting started with custom connectors using remote MCP, https://support.claude.com/en/articles/11175166-getting-started-with-custom-connectors-using-remote-mcp, checked 2026-11-02 (the key-in-URL setup tested end to end).
- Model Context Protocol, Connect to local MCP servers (Claude Desktop), https://modelcontextprotocol.io/docs/develop/connect-local-servers, checked 2026-10-04.
- Cursor Docs, Model Context Protocol, https://cursor.com/docs/context/mcp, checked 2026-10-04.
- OpenAI, Connect and test your plugin, https://developers.openai.com/plugins/deploy/connect-chatgpt, checked 2026-11-04.