How to Connect Claude to Substack (2026 Guide)

Claude is good at the parts of running a newsletter that eat your evenings: turning notes into a draft in your voice, digging through your archive, and making sense of your numbers. Connecting it to Substack is easy if you qualify for Substack's own connector, and still workable if you don't. This guide covers both, as of October 2026.

newsletterapi is an independent project, not affiliated with Substack or Anthropic. We mention our MCP server once at the end; everything else here works today without it.

The problem

You ask Claude to summarise your growth or draft an issue in your voice, and it has nothing to work from. People are working around this with screen-driving agents, which is slow and fragile. One developer testing agents on Substack wrote: "There's no API, Codex will use Safari." (@khemaridh). On Reddit, an agent builder put the root cause plainly: "The issue with substack is that it doesnt have an API." (r/AI_Agents).

In our review of public Reddit, X, Hacker News and GitHub posts, October 2026, 17 distinct sources asked for a way to get their own Substack analytics out, 16 of them since 2025, and the most common workaround we saw was a personal AI agent driving the writer's own logged-in browser. A typical example is a writer's weekly Claude-in-Chrome sync from Substack to Kit. There are safer ways to give Claude your data, and the right one depends on whether you're a Bestseller. More reader problems are on /problems.

Which way of connecting Claude fits me?

Your situation	Best way to connect Claude	What Claude gets
Admin of a Bestseller publication	Substack's official connector	Read-only stats: subscribers, revenue, retention, traffic
Publication with a Publisher API key	Open-source Publisher API server in Claude Desktop or Claude Code	Posts, post stats, daily subscriber counts, single-email lookup
Any writer	Your own exports and RSS feed, uploaded to a Claude project	Your full archive and subscriber data as files
You want Claude to schedule Notes	Buffer's API and MCP (Typefully is the other Notes partner)	Draft and schedule top-level Notes

How do I connect Claude with Substack's official connector?

These are Substack's own steps from its help article:

1. Check eligibility. You must be an Admin on the publication, and it must be a Bestseller publication.
2. Open Claude on desktop or web and click Customize in the left sidebar.
3. Click Connectors, then Add custom connector.
4. Enter https://mcp.substack.com/api/v1/mcp as the MCP server URL and click Add.
5. Sign in to Substack when prompted, then click Allow access. If your account has several publications, pick the Bestseller one.
6. Start a new chat and ask about your publication.

If you see an eligibility error, Substack's note says to check that you're signed in to the account linked to the Bestseller publication.

A few details from Claude's connector guide: custom connectors work on every Claude plan, Free users are limited to one, and on Team or Enterprise an owner adds the connector under Organization settings before members click Connect.

What you can ask, using Substack's own examples: "What's my current subscriber count and revenue?", "How is my paid subscriber retention trending after 6 months?", "Which traffic source drove the most views on my last post?" The connector is read-only. It "cannot publish posts, send Notes, or modify your account", and it can't see your Notes activity.

What if I'm not a Bestseller?

Most writers aren't, so here are the options that don't put your account at risk.

Can I give Claude my own exports?

Substack lets every writer export their data. Settings, Exports, "Create new export" produces a zip of your posts, subscriber list and related statistics (help). The Subscribers page can also export a CSV, with all columns or only the visible ones (help).

Create a Claude project, upload the files, and ask questions. It isn't live, but it is complete, and it is your data. Re-export once a month and replace the files. If the subscriber CSV holds readers' emails, think about whether you need that column for the question you're asking; for most analysis, counts and dates are enough.

Can Claude read my RSS feed?

Every publication has a feed at https://your.substack.com/feed (help). It holds your recent public posts, which is enough for "summarise my last five issues" or "suggest a follow-up to my latest post".

Can I use a Publisher API key?

Some publications have a read-only Publisher API key in their settings. The open-source substack-publisher-mcp wraps it as an MCP server you run from Claude Desktop or Claude Code, following its README. It gives Claude your posts, per-post stats and daily subscriber counts. Its README notes the option "may not be enabled for your publication yet", so check your settings first.

Can Claude schedule my Notes?

If you want Claude to help with Notes, use the partners Substack works with. Buffer says Substack Notes can be created and scheduled through its API and MCP server (Buffer help), Typefully, Substack's other Notes partner, publishes an MCP server that signs in with OAuth; check its current tool list for Notes support before relying on it. Either way, these integrations cover top-level Notes, not long-form posts.

What is Claude actually good at for my newsletter?

Job	What to give Claude	Example prompt
Draft in your voice	Your posts export or a handful of past issues	"Using my last ten posts as a style guide, draft an issue from these notes."
Mine your archive	Posts export	"Which topics have I covered most? What have I promised to follow up on and never did?"
Stats summary	Official connector, Publisher API or exports	"Summarise growth this month: new free, new paid, and which posts drove them."
Retention check	Official connector or subscriber CSV	"How has paid retention changed since the spring?"
Notes ideas	Your latest post	"Give me five Notes that each pull one idea from this post."
Housekeeping	Subscriber CSV	"Group subscribers by signup month and plan type."

Claude is weaker at anything that needs live, per-subscriber events, because Substack doesn't expose them. It also can't publish long-form posts through any official route; for a safe draft-then-paste workflow see publishing to Substack from Markdown.

Should I let Claude publish for me?

Even where a tool can write to Substack, keep the send button for yourself. A newsletter goes to people's inboxes; a bad send can't be recalled. One reader put it well in a discussion of Substack MCP setups: "The manual-approval rule is the right center of gravity, especially with an unofficial API" (comment).

Practical rules:

• Let Claude draft, you paste and publish. Treat its output as a first draft.
• Never give Claude, or any tool, your Substack password or session cookie. Substack's terms forbid "allowing someone else to log into Substack as you", and tools that keep your session in the cloud put the account at risk.
• Prefer OAuth connectors and read-only keys. The official connector and the Publisher API are both read-only, which limits what a confused agent can do.
• Connect only servers you trust. Claude's own help centre warns that custom connectors reach services Anthropic hasn't verified.

Where do I go from here?

For a side-by-side of the official connector, open-source servers and hosted services, read Substack MCP server: official vs open source. For the full list of Substack's developer surfaces, see does Substack have an API.

newsletterapi offers a read-only MCP server for Substack writers that works from your publication URL and your own exports, with no password and no Bestseller requirement, plus a posts API for the same archive. To get access, email hello@newsletterapi.io and tell us what you want to connect first.