MCP Server — Connect Claude, ChatGPT and AI Agents
Connect Claude, Claude Code, ChatGPT or any MCP client to Internal Newsletter at https://internalnewsletter.com/mcp. Five tools to plan, draft, export and measure your internal newsletter, authenticated with your API key.
Internal Newsletter runs a remote Model Context Protocol (MCP) server, so an AI assistant can help you plan, draft, export and measure your internal newsletter from a chat window. There is nothing to install: you point your MCP client at one URL and give it your API key.
https://internalnewsletter.com/mcp
The assistant works on your team's content only, and it never sends email. Exporting gives you email-safe HTML that you paste into Outlook or Gmail and send from your own address, as you would from the app.
What you need
- An Internal Newsletter account. Exporting tracked HTML (
render_for_outlook) needs a paid plan. The other tools work on any plan. - An API key. A team admin creates one in Team Settings → API Keys. The key starts with
inl_and is shown only once, so copy it straight away.- Give it read and write scopes if you want the assistant to create drafts and content.
- A read-only key can look up moments, export HTML and report stats, but it can't create anything.
The key gives access to your whole team's newsletter workspace, so treat it like a password. If it leaks, revoke it in Team Settings and create a new one.
Connect from Claude Code
claude mcp add --transport http internal-newsletter https://internalnewsletter.com/mcp \
--header "Authorization: Bearer inl_your_key"
Then run /mcp inside Claude Code to check that it connected.
Connect from Claude (web and desktop)
Claude's custom connectors don't currently let you set a custom Authorization header, so put the key in the URL instead:
- In Claude, open Settings → Connectors and choose Add custom connector. On Team and Enterprise plans, an organisation owner may need to add it.
- Name it
Internal Newsletter. - For the URL, use
https://internalnewsletter.com/mcp?api_key=inl_your_key. - Leave the OAuth fields empty and save. Then enable the connector in a conversation from the tools menu.
With the key in it, the URL works like a password. Don't share it or paste it anywhere public.
Connect from ChatGPT
ChatGPT accepts remote MCP servers as custom connectors on plans that support developer mode. Menu names change from time to time. Look for Settings → Apps & Connectors → Advanced settings → Developer mode, then create a connector with:
- URL:
https://internalnewsletter.com/mcp?api_key=inl_your_key - Authentication: No authentication. The key in the URL handles it.
Other MCP clients
Any client that supports remote MCP servers over Streamable HTTP will work. If it lets you set headers, send the key as a Bearer token. For example, in clients that use an mcpServers JSON config:
{
"mcpServers": {
"internal-newsletter": {
"url": "https://internalnewsletter.com/mcp",
"headers": { "Authorization": "Bearer inl_your_key" }
}
}
}
Tools
| Tool | Scope | What it does |
|---|---|---|
whats_coming_up |
read | Lists moments worth a mention between from and to (default: the next 14 days). These come from the shared calendar and your team's own events. Where available, each one includes ready-to-use copy: a newsletter blurb, a Slack/Teams post, talking points and a tone note. |
add_update |
write | Saves a piece of news (title, body, optional block_type) to your content library as a draft block. |
draft_issue |
write | Creates a draft issue (title, optional scheduled_date). You can give it existing block_ids, and set include_moments: true to add a block for each upcoming moment that has newsletter copy. It returns the issue id and a link to it in the builder. |
render_for_outlook |
read | Returns the issue as email-safe HTML, the same output as the app's Copy for Outlook button, with open and click tracking built in. It also returns a browser preview link. Paid plans only. |
how_did_it_do |
read | Reports unique opens, unique and total clicks, and the most-clicked links for an issue you exported with tracking. Opens are approximate, so clicks are the more reliable signal. |
Every tool only sees your own team's content. An id from another team is treated as not found.
Example
You might ask the assistant:
"What's coming up in the next two weeks that's worth a mention? Draft next Friday's issue with those moments plus the update about the new parental leave policy."
The assistant would typically call whats_coming_up, then add_update to save the policy news, then draft_issue with include_moments: true and the new block's id. It replies with a link to the draft in the builder, where you check the issue and reorder anything before you export it.
Here is the same first step over raw HTTP, if you want to test the endpoint:
curl -s https://internalnewsletter.com/mcp \
-H "Authorization: Bearer inl_your_key" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whats_coming_up","arguments":{}}}'
Technical details
- Transport: MCP Streamable HTTP. Each
POST /mcpreturns a single JSON response. The server doesn't stream over SSE, doesn't use sessions, and doesn't send notifications on its own. - Methods:
initialize,ping,tools/list,tools/call. Notifications are acknowledged with202 Accepted. - Protocol versions:
2025-11-25,2025-06-18,2025-03-26and2024-11-05. The server uses your client's version if it's on that list. - Auth errors: a missing, revoked or expired key returns
401with aWWW-Authenticate: Bearerheader. - Rate limit: 60 requests per minute per API key, the same as the REST API.