Substack MCP Server

Posts, Notes, messages, subscribers and stats for your publication.

Barındırılan MCP Sunucusu

npx add-mcp 'https://cotlet.dev/mcp/v1/substack'

Claude Code, Codex, Cursor ve daha fazlasına kurulur

Dokümantasyon

Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up

Substack API and MCP server: Let your AI agent run your Substack newsletter.

Substack's official MCP server reads dashboard stats for Bestseller publications, and nothing official writes drafts, Notes or replies (checked 24 Oct 2026). Cotlet runs 50 Substack tools that read and write, hosted, over MCP for agents and REST for scripts.

Read your Substack posts and publication reports through MCP or REST. Use an AI agent, n8n, Make, Zapier or a script to build your publishing workflow.

Connect an AI agent Use the REST API

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Substack. Substack is a trademark of its owner. If Substack's own integrations cover what you need, use them first.

What can you automate in Substack?

  • Turn Markdown into a draft
  • Schedule the weekly issue
  • Post Notes about new posts
  • Answer comments you missed
  • Report subscribers and revenue
  • Tag and add subscribers

Does Substack have an official API or MCP server?

  • The official server at mcp.substack.com needs an Admin of a Bestseller publication, which takes hundreds of paid subscribers. It reads metrics, traffic and settings. It "cannot publish posts, send Notes, or modify your account", and it cannot see Notes activity.
  • A read-only Publisher API gives posts, post stats and subscriber lookups where Substack has switched it on for a publication. The Developer API returns public creator profiles only. There are no webhooks and no Zapier or n8n app.
  • Community MCP servers on GitHub write drafts and Notes from your own computer, on a session cookie copied from your browser.
What you needSubstack MCP (official)GitHub MCP serverCotlet
Subscriber, revenue and traffic statsYes, Bestseller onlySomeYes, no badge needed
Drafts, scheduling and publishingNoSomeYes, with your OK
Notes, comments and DMsNoSomeYes
Runs with your computer offYesNoYes, hosted
Fixed for you when Substack changesYesNoYes

Checked 24 Oct 2026. Sources: Substack: How to connect Substack to your AI Assistant, Substack: What is a Bestseller badge?, Substack Developer API Terms of Use, Substack features (scheduling, import, export, Notes, stats)

How does Cotlet connect to Substack?

  1. Sign in to Substack. One time, in your own Cloud Browser.
  2. Choose MCP or REST. Connect an AI agent or create a Cotlet API key for HTTP requests.
  3. Run your workflow. Ask your agent or call the REST API.

Your Substack password never reaches us. Posts, Notes and replies wait for your OK.

Connect Substack to your AI agent or workflow

Use MCP with ChatGPT, Claude, Cursor or Codex. For n8n, Make or Zapier, use authenticated HTTP or a supported MCP client. The agent setup is below; the REST guide follows.

Step by step with screenshots for ChatGPT, Claude, Grok and other agents: How to connect Substack to Claude or ChatGPT and let AI do the work.

  1. Enable Substack for agents. Sign up, sign in to Substack in its Cloud Browser and press Enable for agents.
  2. Add the Substack address. Paste https://cotlet.dev/mcp/v1/substack into your agent's MCP or connector settings.
  3. Sign in or paste a key. Chat apps sign you in to Cotlet; editors and scripts take an API key from the console.

Already use Substack's own connector for stats? Keep it, and add this one under another name for drafts, Notes and comments.

Claude:

Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect

Claude Code:
claude mcp add --transport http cotlet-substack \
  https://cotlet.dev/mcp/v1/substack \
  --header "Authorization: Bearer $COTLET_API_KEY"

ChatGPT:

Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth

Cursor:

// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet-substack": {
      "url": "https://cotlet.dev/mcp/v1/substack",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}

Codex:

# ~/.codex/config.toml
[mcp_servers.cotlet-substack]
url = "https://cotlet.dev/mcp/v1/substack"
bearer_token_env_var = "COTLET_API_KEY"

n8n:

MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: substack_read

Make, Zapier:

Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: substack_write

How to use the Substack REST API

Create your Cotlet API key

Sign in to Substack in your Cloud Browser and enable it for agents. Create a Cotlet API key scoped to Substack; read-only access is enough for this example.

Store the key in your environment as COTLET_API_KEY. Use your Cotlet key, not your Substack password.

Make your first Substack API request

This GET /posts request reads recent published posts. Cotlet uses the first publication your signed-in account administers; there is no publication selector or arbitrary newsletter scraping.

cURL: list_posts:

curl "https://cotlet.dev/api/v1/substack/posts?status=published&limit=10" \
  -H "Authorization: Bearer $COTLET_API_KEY"

Read the response and fetch more posts

A successful REST call returns status: "success" with the tool output in result. This JSON excerpt uses example data and omits call IDs, messages and credit details.

Example response excerpt:

{
  "status": "success",
  "app": "substack",
  "tool": "list_posts",
  "result": {
    "posts": [
      {
        "post_id": "148213977",
        "title": "The quiet launch",
        "status": "published",
        "audience": "everyone",
        "published_at": "2026-10-06T12:00:00Z",
        "url": "https://yourname.substack.com/p/the-quiet-launch"
      }
    ],
    "next_cursor": null
  }
}

Read result.posts, then pass result.next_cursor unchanged as cursor with the same status and limit. Stop when it is null. A full final page can require one extra request that returns no posts.

Substack workflows with n8n, Make and Zapier

ToolConnect throughExample workflow
n8nHTTP RequestRead recent published posts, then fetch post stats for a daily performance snapshot of each post. Save it through your reporting steps.
MakeHTTP > Make a requestRead draft and scheduled posts in separate calls, compare the queues and build a weekly editorial report.
ZapierWebhooks by Zapier > GET or Custom RequestAfter a delay you configure, fetch stats for a chosen published post and send a report to your spreadsheet or email steps.

Send Authorization: Bearer <your Cotlet API key> in the request headers. Configure the schedule and destination in your chosen tool. Cotlet reads the app data; your destination steps perform any spreadsheet, email or team-channel writes.

These are workflows you configure, not native connectors or prebuilt templates. Read periodically and track handled IDs to avoid duplicates; these workflows do not depend on outgoing app event webhooks.

get_post_stats uses GET /posts/{post_id}/stats with a published post ID. Drafts and scheduled posts have no stats yet. open_rate is a fraction, so 0.488 means 48.8%; values evolve after publication. These reporting workflows do not publish anything.

Python or Node.js can make the same REST calls without an AI agent or an SDK. Use your own signed-in account and its first administered publication.

The API and MCP reference lists every method, path and input. The REST API guide covers request format, errors and approvals.

Substack API endpoints and MCP tools

Posts, drafts and sections

A sent email stays sent. Unpublish keeps the post as a draft; delete has no undo.

  • List posts (list_posts, read): Posts of your publication, newest first, with status and audience.
  • Get post (get_post, read): Full post: title, subtitle, body as Markdown, audience, URL and dates.
  • Create draft (create_draft, write): New draft from Markdown. Nothing is sent until you publish or schedule it.
  • Update draft (update_draft, write): Change the title, subtitle, body or audience of a draft.
  • Duplicate post (duplicate_post, write): Copy any post into a new draft.
  • Schedule post (schedule_post, write, asks first): Publish a draft at a set time, on the web and by email.
  • Cancel scheduled post (cancel_scheduled_post, write): Stop a scheduled post from going out; it stays as a draft.
  • Publish post (publish_post, write, asks first): Publish a draft now.
  • Unpublish post (unpublish_post, write, asks first): Take a published post off the web and back to drafts.
  • Delete post (delete_post, write, asks first): Delete a draft, scheduled or published post, with its comments.
  • List sections (list_sections, read): Sections of your publication, the separate newsletters inside it.
  • List post tags (list_post_tags, read): Tags your publication uses to group posts.
  • Create post tag (create_post_tag, write): New tag for grouping your posts.
  • Tag post (tag_post, write): Add a tag to a post, or take it off.

Notes, feed and people

Notes take up to 1,000 characters and are not emailed. Likes and follows run without asking, and the author sees them.

  • List Notes (list_notes, read): Notes posted by you or any other Substack user, newest first, with likes and replies.
  • List Note replies (list_note_replies, read): Replies under a Note, with author, text and likes.
  • Publish Note (publish_note, write, asks first): Short post in Substack Notes, now or at a set time, optionally with a link card to one of your posts.
  • Reply to Note (reply_to_note, write, asks first): Reply as you under any Note or Note reply.
  • Get feed (get_feed, read): Your Substack home feed: posts and Notes, For you or Following.
  • Search Substack (search_substack, read): Search all of Substack for people, posts and Notes.
  • Follow user (follow_user, write): Follow or unfollow a Substack user, so their Notes reach your feed.
  • Like post (like_post, write): Like or unlike any Substack post as you.
  • Like comment or Note (like_comment, write): Like or unlike a comment or a Note as you.
  • List activity (list_activity, read): Your Substack notifications: replies, likes, new followers, restacks, newest first.

Comments

On your own publication's posts only. Remove hides a reader's comment as moderator; delete is for your own.

  • List comments (list_comments, read): Comments on a post, with author, text and whether you replied.
  • Reply to comment (reply_to_comment, write, asks first): Reply as you under a comment on your post.
  • Pin comment (pin_comment, write): Pin a comment to the top of your post's comments, or unpin it.
  • Remove comment (remove_comment, write, asks first): Remove someone's comment from your post as the publication's moderator.
  • Delete comment or Note (delete_comment, write, asks first): Delete one of your own comments, Notes or Note replies.

Subscribers and tags

Adds free subscribers only. Removing a paid one cancels the plan and Substack refunds the rest.

  • List subscribers (list_subscribers, read): Subscribers with plan, start date and activity rating.
  • Export subscribers (export_subscribers, read): The full subscriber list as a CSV download link, with the row count.
  • Add subscriber (add_subscriber, write, asks first): Add one email to your list as a free subscriber.
  • Remove subscriber (remove_subscriber, write, asks first): Remove one email from your subscriber list.
  • List subscriber tags (list_subscriber_tags, read): Tags you use to group subscribers.
  • Create subscriber tag (create_subscriber_tag, write): New private tag for grouping subscribers.
  • Tag subscribers (tag_subscribers, write): Put a tag on subscribers by email, or take it off.
  • List subscriptions (list_subscriptions, read): Publications you subscribe to, with your plan and whether their emails reach you.

Direct messages

A message cannot be recalled. Someone who does not follow you gets it as a request.

  • List conversations (list_conversations, read): Your direct-message conversations, latest first, with the last message.
  • Get conversation (get_conversation, read): The latest messages of one direct-message conversation, oldest first.
  • Send message (send_message, write, asks first): Send a direct message on Substack, in a conversation or to a person.
  • Get unread counts (get_unread_counts, read): How many unread direct messages, message requests and activity notifications you have.

Stats, growth and recommendations

Dashboard numbers for your publication. Revenue is Substack's annualized run rate, not cash received.

  • Get publication stats (get_publication_stats, read): Total and paid subscribers, new subscribers, paid cancellations and estimated revenue for a period.
  • Get post stats (get_post_stats, read): Recipients, opens, open rate, views, likes, restacks and subscribers gained.
  • Get daily stats (get_daily_stats, read): Day by day: total and paid subscribers, followers and views.
  • Get post engagement (get_post_engagement, read): Who liked and commented on a post, and the subscribers it won and lost.
  • Get post traffic (get_post_traffic, read): Where a post's readers came from: sources, categories and devices.
  • List traffic sources (list_traffic_sources, read): Where your publication's visitors came from in a period, most views first.
  • Get audience insights (get_audience_insights, read): Where your subscribers live, and which publications share your readers.
  • List recommendations (list_recommendations, read): Publications you recommend, or that recommend you, with the subscribers each sent.
  • Recommend publication (recommend_publication, write, asks first): Recommend another publication to your readers, or stop recommending it.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/substack-api-mcp-server#tools

Who can see my Substack session, and how do I revoke it?

  • What we store. The Substack sign-in of your Cloud Browser, AES-256-GCM, on servers in Finland. No password.
  • What your agent gets. Substack tools only, never your sign-in cookie.
  • What the session sees. What your role in the publication sees: drafts, subscriber emails, DMs, revenue.
  • What we log. Time, tool and status. Not the post text or any email address.
  • If Substack signs you out. We email you a sign-in link. We never type your password.
  • How to cut access. Disable Substack for agents, reset its browser or delete the key.

Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).

Approvals, undo and mistakes

  1. Reads essay.md. Title, subtitle, Markdown body, images by URL.
  2. Checks the calendar. Stops if an issue is already set for that day.
  3. Waits for your OK. The send time shows up in your Cotlet console.
  4. Reports back. Send time, audience and the editor link.

13 of 50 tools ask first: anything readers get, every delete and every removal. Drafts, tags and likes run straight away. Turn the wait off per tool for scheduled runs.

ActionUndo
Publish a postThe web post: unpublish. The email: no
Schedule a postYes, until it goes out
Delete a postNo, Substack has no undo
Remove a paid subscriberNo, Substack refunds and cancels
Send a DMNo

MCP call:

{
  "name": "schedule_post",
  "arguments": {
    "post_id": "148420031",
    "publish_at": "2026-10-13T08:00:00-04:00",
    "send_email": true
  }
}

REST:

curl -X PUT https://cotlet.dev/api/v1/substack/posts/148420031/schedule \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"publish_at":"2026-10-13T08:00:00-04:00","send_email":true}'

Tool output:

{
  "post_id": "148420031",
  "status": "scheduled",
  "publish_at": "2026-10-13T08:00:00-04:00",
  "audience": "everyone",
  "url": "https://yourname.substack.com/p/notes-on-pricing"
}

For read-only onboarding, see the REST API guide on this page. A post without a title or body fails Substack's own pre-publish check and costs nothing.

How much do the Substack API and MCP server cost?

About $19 a month for a weekly newsletter that also posts Notes and answers comments, 3,260 credits.

JobCallsCredits
Draft and schedule the weekly issue3 × 4120
Three Notes a week3 × 4120
Check for unanswered comments, daily4 × 301,200
Reply to about four comments a week4 × 4160
Subscriber and revenue report, weekly4 × 4160
Cloud Browser, 30 days1,500
Total3,260
  • Free 7-day trial, no card
  • 10 credits per successful call, MCP or REST
  • 50 credits a day for the Cloud Browser
  • One-time packs, valid 12 months, no subscription

The cadence follows WriteStack's sample of 25 Jul 2026: the median active publication posts about once a week, and a post averages about 4 comments. Dollars at the $29 pack rate.

Substack MCP server on GitHub, official or hosted: which to use

OptionWhat it doesWhere it stops
marcomoauro/substack-mcpThe most starred Substack MCP server (90 stars): posts and drafts on your session.Runs on your computer; last commit 3 Sep 2026.
conorbronsdon/substack-mcpDrafts, Notes, analytics and subscribers across publications (44 stars).Creates and edits drafts, does not publish or delete; a cookie you copy.
dkships/substack-publisher-mcpWraps the official Publisher API with a key instead of a cookie.Read only, and only where Substack has switched the API on.
jakub-k-slys/substack-apiTypeScript client for the private API (99 stars) and an n8n community node.A library, not a server; Notes from n8n have failed with 403 for some users.
NarrareachHosted scheduler with its own MCP, also for Medium, LinkedIn and X.$19.99 to $89 a month; built around cross-posting.

Pick Substack's connector if you have a Bestseller badge and want numbers only. Pick a GitHub server if you want the code on your machine and can paste a fresh cookie when it expires. Pick Cotlet if an agent should draft, schedule and answer readers every week without you running anything.

Run our Substack MCP server on your own computer

The same Substack tools are public on GitHub, as an MCP server and REST API in Python. Run them with your own Chrome against a test publication and read how each one talks to Substack. It is a trimmed copy of what runs on cotlet.dev, free to use in your own business.

  • Free for personal use, learning and testing
  • Works while your computer is on, signed in through your own Chrome
  • When Substack changes, you pull the fix yourself
  • License Elastic 2.0: free in your own business; ChatGPT, your phone and 24/7 runs need hosted Cotlet
  • Code: https://github.com/cotletdev/substack-api-mcp-server

Also listed on: Odel, mcpbeat

Who runs Cotlet

Cotlet is run by Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273), working since 2019. The founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Substack tools go to contact@cotlet.dev.

Substack API and MCP: frequently asked questions

Can I use Substack with n8n, Make or Zapier through Cotlet?

Yes. Use authenticated REST requests or a supported MCP client. Configure schedules, destinations and record tracking in your chosen automation tool. The REST section above gives app-specific workflows.

Can I use the Substack API without an AI agent?

Yes. A script or HTTP step can call the REST endpoints with your Cotlet API key. Sign in to the app in your Cloud Browser first; no agent connection is required.

How do I get access?

Sign up free at https://cotlet.dev, open Substack under Integrations in the console and sign in to Substack in its Cloud Browser. Your free trial starts when you sign up, no card needed.

How do I connect Substack to ChatGPT or Claude?

Sign up at cotlet.dev, log in to Substack once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Substack account through Cotlet, in their phone apps too.

What can ChatGPT do in Substack?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Substack: schedule newsletter posts from a Markdown draft; post a Note when a new post goes out; weekly subscriber growth and revenue report. You ask in plain words, and anything that reaches other people waits for your OK first.

Can it schedule Notes as well as posts?

Yes. publish_note takes a publish_at time and the Note waits in your scheduled Notes until then. Substack added Notes scheduling in its apps; see On Substack, linked in the sources.

Does it need a paid Substack plan?

No. It acts as the Substack account you sign in with and works on the first publication that account runs as admin, owner, editor or contributor.

What can it not do yet?

It cannot give complimentary paid plans: add_subscriber adds free subscribers only. Buttons, embeds and footnotes read back as plain text, and list_subscribers cannot filter by tag. Recommendation tables and audience locations are rebuilt by Substack in the background, so a new publication sees them empty for a while. It never changes your Substack password, email, sign-in or profile. If Substack suspends your account, every call returns an error that says so.

Is this the same as Substack's own MCP server?

No. Substack's server at mcp.substack.com is official and reads stats for Bestseller publications. Ours is unofficial, uses the first publication your signed-in account administers and also writes: drafts, scheduling, Notes, comments, DMs and subscribers. You can connect both.

Does Substack have webhooks?

No. Substack sends no events out, and its RSS feed carries public posts only. To react to new comments or subscribers, run your agent on a schedule and read them.

Is the MCP server different from the REST API?

Only the way in. Both have the same 50 tools, inputs and answers, one API key and one price.

Is Cotlet affiliated with Substack?

No. Cotlet is independent and not affiliated with Substack Inc.


Give your AI agents your signed-in browser.

Product: Integrations · How it works · Pricing · Security

Resources: Blog · API docs · Help center · Changelog · GitHub

Solutions: For developers · For automation agencies

Company: About · AI info: company facts · Contact

Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors

Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.