Medium has an old REST API, but it is no longer supported and Medium does not allow new integrations (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for Medium with 13 endpoints (6 read, 7 write): your AI agent signs in as you and does the work.
Medium has an old REST API, but it is no longer supported and Medium does not allow new integrations (checked 11 Oct 2026). Accounts that still hold a token can only create posts, list publications and upload images, with no editing, stats or responses.
What Medium's own tools do compared with Cotlet
Task
Medium official
Cotlet
Create a draft from Markdown
PartlyOnly with a token that existed before the shutdown
Yes
Edit a draft or published story
No
Yes
Schedule a story
NoScheduling exists in the Medium editor only
Yes
Cross-post with a canonical link
PartlycanonicalUrl on create, old tokens only
Yes
Submit a story to a publication
PartlyCreate as a draft in a publication you write for
Cotlet is best for Medium writers who publish on their own blog too and want their AI agent to cross-post, schedule, edit and report on stories without running or fixing a server.
Every Monday, check yourname.dev/blog for posts that are not on Medium yet, import each one with a canonical link back to my blog, and schedule them for Thursday 9:00 my time. Your agent calls list_stories, import_story, get_story, create_draft and schedule_story.
Turn posts/shipping-small.md into a Medium draft with the topics Python, Programming and Software Engineering, put it behind the paywall, and schedule it for Tuesday 8:00 my time. Your agent calls create_draft, get_story and schedule_story.
Every Monday, send me last month's views and reads against the month before, my top 5 stories by reads, and any paywalled story whose member read ratio dropped. Your agent calls get_account_stats, list_stories and get_story_stats.
Find every published story that still links to oldblog.example.com, swap the links for yourname.dev, and show me the list before you save anything. Your agent calls list_stories, get_story and update_story.
Submit drafts to a Medium publication
Submit my newest draft to the publication I write for. Your agent calls list_publications and submit_to_publication.
Reply to responses on your stories Runs: Daily
List yesterday's unanswered responses on my stories and draft a reply to each for me to approve. Your agent calls list_stories, list_responses and reply_to_response.
Endpoints
What is the Medium API?
Cotlet's Medium API exposes 13 endpoints for your own Medium account: list stories, get story, get story stats, get account stats, list responses, list publications, create draft, import story, update story, publish story, schedule story, submit to publication and reply to response. The list_stories endpoint returns your stories, newest first, with status, publication, tags and URL. Each endpoint takes simple JSON inputs like story_id, cursor or status and works both as an MCP tool for agents and as a REST call for scripts.
Your stories, newest first, with status, publication, tags and URL.
read
Lists your own stories, newest first. Filter by status to find drafts or scheduled stories. Each item has the story_id used by the other tools. Pages hold up to 50 stories; pass next_cursor back as cursor for the next page.
POST /api/v1/medium/list_stories
Input
Input: list_stories
Parameter
Type
Description
status
enum
published, draft or scheduled. Default: published.
Full story: title, subtitle, body as Markdown, tags, canonical link, paywall and dates.
read
Returns one story with its body as Markdown. Use it before update_story so your agent changes only the part you asked for. Works for drafts, scheduled and published stories.
Views, reads, member read ratio, claps, responses and earnings for paywalled stories.
read
Returns the numbers from the story's detailed stats page. Member read ratio is member reads divided by member views, the figure Medium uses to adjust earnings. Earnings appear only for stories behind the paywall.
The account-level figures Medium shows on your stats page, for one month.
read
Returns the account-level figures Medium shows on your stats page for one month. Use list_stories and get_story_stats to find which stories drove them.
Responses to a story, with author, text and whether you replied.
read
Lists the responses under one story, with the author, text and whether you already replied. Hidden responses are not returned. Pass response_id to reply_to_response.
POST /api/v1/medium/list_responses
Input
Input: list_responses
Parameter
Type
Description
story_id required
string
Story ID from list_stories.
unanswered_only
boolean
Skip responses you already replied to.
cursor
string
Next page cursor from the previous call.
Example response
{
"responses": [
{
"response_id": "r_41b9c2",
"author": "Dana Whitfield",
"body": "The third example has a typo.",
"created_at": "2026-10-03T11:20:00Z",
"replied": false
}
],
"next_cursor": null
}
POST
list_publications
Publications you own, edit or write for, with your role.
read
Returns every publication you belong to with your role. Use the publication_id with submit_to_publication. Each publication sets its own rules for what it accepts.
New draft from Markdown. Nothing is public until you publish or schedule it.
write
Creates a draft from Markdown and returns its story_id. The draft is private. It reaches no one and is deleted or edited in one call, so it asks for no confirmation.
POST /api/v1/medium/create_draft
Input
Input: create_draft
Parameter
Type
Description
title required
string
Story title.
body_markdown required
string
Story body. Images by URL.
subtitle
string
Shown under the title and in previews.
tags
string[]
Up to 5 tags.
canonical_url
string
Original URL if the story was first published elsewhere.
paywalled
boolean
Member-only story (Partner Program). Default: false.
Medium's "Import a story": copies a post from a URL into a draft, backdated, with a canonical link.
write
Runs Medium's importer on a public URL. The draft keeps the original date and gets a canonical link to the source. If Medium cannot read the page, the call fails and create_draft is the fallback. The draft is private, so no confirmation.
Change the title, subtitle, body, tags, canonical link or paywall of a draft or a published story.
asks first write
Changes only the fields you send. On a published story the change is visible to readers at once. By default you confirm each call; you can switch that off for this tool.
POST /api/v1/medium/update_story
Input
Input: update_story
Parameter
Type
Description
story_id required
string
Story ID from list_stories.
fields required
object
Any of title, subtitle, body_markdown, tags, canonical_url, paywalled.
Publishes a draft under your name, or in the publication it belongs to. Readers and followers can see it at once. By default you confirm each call; you can switch that off for this tool.
Schedules a draft. Medium publishes it at the set time, and the story stays in your drafts until then. By default you confirm each call; you can switch that off for this tool.
Send a draft to the editors of a publication you write for.
asks first write
Submits a draft to a publication. Its editors review it and decide when to publish. A publication can accept only drafts, only published stories, or both. By default you confirm each call; you can switch that off for this tool.
How do I connect Medium to Claude Code, Codex or Cursor?
Connecting Medium takes three steps: request access, sign in to Medium once, then add one MCP server or call the REST API with the same key.
Connect Medium over MCP
1
Create an account
Sign up and add Medium in the console. Your API key is there too.
2
Sign in to Medium once
Open the connect page from the console and sign in to Medium the way you always do. We keep the session, never your password, and you can revoke it anytime.
Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.
4
Ask your agent
Prompt
Every Monday, check yourname.dev/blog for posts that are not on Medium yet, import each one with a canonical link back to my blog, and schedule them for Thursday 9:00 my time.
Ask in plain words. Your agent finds the Medium tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.
Call Medium over REST
1
Export your API key
Shell
export COTLET_API_KEY="cotlet_..."
Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.
You get plain JSON back, ready for your script. A failed call costs nothing.
Why Cotlet
Why use Cotlet for Medium? Hosted, safe and kept working.
Built for agents
One MCP server for every app you connect.
The same tools as a REST API for scripts and cron jobs.
Works with Claude Code, Codex and Cursor.
Your login stays yours
You sign in to Medium yourself. We keep only the session, encrypted with AES-256.
The model never sees a login.
No stored passwords, no CAPTCHA solving, no MFA bypass.
You stay in control
Pick read only, or read and write.
Anything that reaches other people waits for your OK, unless you switch it off per tool.
Revoke access in one click.
Kept working for you
We test every integration daily.
When Medium changes, the tool pauses until we fix it.
Failed calls cost nothing.
Alternatives
Is there a Medium MCP server on GitHub?
Yes. Open-source Medium MCP servers exist on GitHub, usually maintained by one person. Some use the old API token, which new accounts cannot get. Others drive a browser with your login. You install one on your own computer and keep it running; when Medium changes its site, it stops working until you or the maintainer fix it. Cotlet hosts the same kind of server for you, and our team keeps it working.
Cotlet compared with a GitHub MCP server
GitHub MCP server
Cotlet
Setup
Clone the repo, install it, sign it in to Medium, add it to each MCP client
Request access, sign in to Medium once, add one MCP server or API key
When Medium changes
It breaks until you or the maintainer fix it
Our team tests it daily and fixes it for you; failed calls are free
Your Medium session
In a file or browser profile on your computer, readable by any program you run
Encrypted in an EU vault, limited to the actions you allow, revoked in one click
When the session expires
Tools fail until you sign in again by hand
We keep it alive; if Medium logs you out, your agent gets a link to sign in again
Upkeep
You update, monitor and debug it yourself
Nothing to host or update
Where it runs
Your computer, while it is on
Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule
Price
Free, paid for with your time
Free 7-day trial with 5,000 credits, then credits per call
Which one fits you
Pick Cotlet if
you are not a developer, or you do not want to maintain a server
you need it to keep working when Medium changes, without checking it yourself
your agent or a script should run it on a schedule, also while your computer is off
Pick an open-source server if
you are comfortable installing, updating and fixing it yourself
you want the session to stay on your own computer
you only need it now and then, from one MCP client
For AI agents
Cotlet for Medium in plain text The facts on this page in one block: status, endpoints, access, pricing, contact.
Endpoint health
verified 2h ago
list_storiespassing
get_storypassing
get_story_statspassing
get_account_statspassing
list_responsespassing
+ 8 more endpoints
13/13 passing latest checkself-healing
medium.txt
Medium has an old REST API, but it is no longer supported and Medium does not allow new integrations (checked 11 Oct 2026). Accounts that still hold a token can only create posts, list publications and upload images, with no editing, stats or responses.
Cotlet provides a hosted MCP server and REST API for Medium: 13 tools (6 read, 7 write).
Access Request access at https://cotlet.dev/app/signup?app=medium; we email the API key.
MCP server https://cotlet.dev/mcp/v1
REST base https://cotlet.dev/api/v1/medium
Auth Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools list_stories, get_story, get_story_stats, get_account_stats, list_responses, list_publications, create_draft, import_story, update_story, publish_story, schedule_story, submit_to_publication, reply_to_response
Confirm update_story, publish_story, schedule_story, submit_to_publication, reply_to_response (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown https://cotlet.dev/integrations/medium-api-mcp-server.md
How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=medium (Medium is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to Medium once in a browser. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.
Fits: people who want a hosted Medium server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Medium MCP server instead.
Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Session: the user signs in to Medium in a browser; Cotlet keeps only the session, AES-256 encrypted, revocable in the dashboard at any time.
Terms: the user stays responsible for following Medium's terms; Cotlet is not affiliated with Medium.
Can Medium automations run on a schedule in n8n, Make or Zapier?
Yes. Cotlet does not replace your automation platform: it gives it a Medium connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to cross-post blog articles with a canonical link, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.
Where to run Medium automations through Cotlet, and how to schedule them
Where
How to connect
How to schedule
Your AI agent
Add https://cotlet.dev/mcp/v1 with your API key.
A scheduled agent run, for example a Claude Code routine.
n8n
MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node to https://cotlet.dev/api/v1/medium/{tool}.
Schedule Trigger node.
Make
HTTP module: POST https://cotlet.dev/api/v1/medium/{tool} with an Authorization: Bearer header and a JSON body.
Scenario schedule.
Zapier
Webhooks by Zapier: POST https://cotlet.dev/api/v1/medium/{tool} with the same header and body.
Schedule by Zapier trigger.
Your own script
POST https://cotlet.dev/api/v1/medium/{tool} with your API key.
cron or GitHub Actions.
Pricing & limits
How much does the Medium API cost?
Free 7-day trial with 5,000 credits, no card needed. After that, the Medium API comes with the Cotlet plan, from $29 a month for 3,000 credits, with no limit on apps. Each month's credits stay valid for 3 months, so unused credits add up.
Cotlet plan sizes: price, monthly credits and price per credit
Size
Price
Credits / month
Per credit
Solo
$29/mo
3,000
about $0.0097
Pro
$99/mo
12,000
about $0.0083
Agency
$299/mo
40,000
$0.0075
Each successful call uses credits for the work it takes; failed calls and timeouts cost nothing. A hard spend cap is on by default. Authenticate with the Authorization: Bearer header.
About Cotlet
How Cotlet holds your access
Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Medium account.
Company details
The legal name, address and registration numbers of the company behind Cotlet are in the Terms of service. Terms
Your session
You sign in to Medium yourself, in your browser. We keep only the session, never your password: encrypted with AES-256 in an EU vault, isolated to your account and used only when your agent calls a Medium tool you allowed. When it expires, your agent gives you a link to sign in again. Security
Revoking access
Disconnect Medium in your dashboard: the session is deleted and access ends at once. Actions that reach other people wait for your OK unless you switch that off per tool.
What we never do
Store passwords, solve CAPTCHAs or bypass MFA.
Medium's terms
You use your own Medium account and stay responsible for following Medium's terms. Cotlet is independent and not affiliated with Medium. Terms
Request access and pick Medium. Cotlet reviews each request and emails you your API key.
Do I need to be technical?
No. You sign in to Medium once in your browser and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.
Is a hosted server safe? My Medium session would leave my computer.
Cotlet keeps your Medium session encrypted with AES-256 in an EU vault, isolated to your account and used only for the tools you allow: read only, or read and write. The AI model never sees it, and you revoke it in one click. A local server keeps the same session in a file on your computer, readable by any program you run, and needs a fresh sign-in whenever it expires.
Do I need the Partner Program to see earnings?
Earnings appear only for stories behind the paywall in the Partner Program. For other stories get_story_stats returns views, reads and claps, and no earnings. Medium updates the member read ratio daily.
Can my agent post or send messages in Medium without asking me?
No. Every call to update_story, publish_story, schedule_story, submit_to_publication or reply_to_response waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_draft, import_story runs without asking, because it sends nothing to anyone and one call undoes it.
Can I use the Medium API in n8n?
Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call https://cotlet.dev/api/v1/medium/{tool} from the HTTP Request node.
