Medium-ops MCP Server

Medium CLI + 23-tool MCP server. Your IDE drafts replies. No API keys.

Local serverstdio

What is the Medium-ops MCP Server?

Medium-ops is an MCP integration. Medium CLI + 23-tool MCP server. Your IDE drafts replies. No API keys.

Packages and local setup

The published pypi package is medium-ops, version 0.1.2. Its declared MCP transport is stdio.

The package declares MEDIUM_INTEGRATION_TOKEN: Legacy Medium Integration Token (api.medium.com/v1/). Optional. Generate at medium.com/me/settings → 'Integration tokens' (note: Medium stopped issuing new tokens in 2023).; MEDIUM_SID: Medium 'sid' cookie value from medium.com (Application → Cookies). Used for authenticated reads + dashboard GraphQL.; MEDIUM_UID: Medium 'uid' cookie value. Required alongside sid for some authenticated endpoints.; MEDIUM_XSRF: Medium 'xsrf' cookie value. Required for any dashboard write (post_response, publish_post, delete_post, draft updates).; MEDIUM_CF_CLEARANCE: Cloudflare 'cf_clearance' cookie. Only required when Cloudflare challenges your IP for dashboard write calls.; MEDIUM_USERNAME: Your Medium handle (without the @). Required for the public RSS read path so the client knows whose feed to fetch.; MEDIUM_OPS_MCP_PATH: Override path to the mcp.json file the auth layer reads. Defaults to ~/.cursor/mcp.json.; MEDIUM_OPS_LLM_CMD: Optional: override the host CLI used by the unattended daemon path (default: auto-detect claude / cursor-agent / codex on PATH). Use {prompt} placeholder if your CLI takes the prompt as an arg..

This package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.1.2 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
MEDIUM_INTEGRATION_TOKENLegacy Medium Integration Token (api.medium.com/v1/). Optional. Generate at medium.com/me/settings → 'Integration tokens' (note: Medium stopped issuing new tokens in 2023).Optional
MEDIUM_SIDMedium 'sid' cookie value from medium.com (Application → Cookies). Used for authenticated reads + dashboard GraphQL.Optional
MEDIUM_UIDMedium 'uid' cookie value. Required alongside sid for some authenticated endpoints.Optional
MEDIUM_XSRFMedium 'xsrf' cookie value. Required for any dashboard write (post_response, publish_post, delete_post, draft updates).Optional
MEDIUM_CF_CLEARANCECloudflare 'cf_clearance' cookie. Only required when Cloudflare challenges your IP for dashboard write calls.Optional
MEDIUM_USERNAMEYour Medium handle (without the @). Required for the public RSS read path so the client knows whose feed to fetch.Optional
MEDIUM_OPS_MCP_PATHOverride path to the mcp.json file the auth layer reads. Defaults to ~/.cursor/mcp.json.Optional
MEDIUM_OPS_LLM_CMDOptional: override the host CLI used by the unattended daemon path (default: auto-detect claude / cursor-agent / codex on PATH). Use {prompt} placeholder if your CLI takes the prompt as an arg.Optional