minanagehsalalma/medium-editor-mcp
GitHub: minanagehsalalma/medium-editor-mcp
Stars: 0 | Forks: 0
# Medium Editor MCP
sid + uid + xsrf] --> B[Session setup + doctor] B --> C{Surface selection} C --> D[GraphQL replay
settings, publish, metadata] C --> E[Legacy delta editor
body writing, image blocks, repairs] C --> F[Browser validation
fallback only] G[Gist / markdown / source notes] --> H[Draft audit + optimization] H --> E D --> I[Post workflows] E --> I F --> I I --> J[Draft, publish, repair,
replace, delete, restore] ## Tooling Map | Layer | What it covers | Main tools | | --- | --- | --- | | Session | Cookie parsing, redaction, diagnostics, transport health | `setup-medium-session`, `inspect-medium-session-config`, `doctor-medium-mcp`, `probe-medium-session` | | GraphQL | Discovery, replay, operation capture, live metadata/publish workflows | `discover-medium-graphql`, `capture-medium-graphql-operations`, `medium-graphql-request`, `run-medium-graphql-operation` | | Legacy editor | Real body writing and delta-based post repair | `create-medium-legacy-draft`, `apply-medium-legacy-deltas`, `write-medium-rich-draft`, `create-medium-rich-draft` | | Content pipeline | Gist import, GitHub repo import, draft audit, package optimization, article restructuring | `import-gist`, `prepare-gist-draft`, `import-github-repo`, `prepare-github-repo-draft`, `audit-medium-draft`, `optimize-medium-draft-package`, `optimize-medium-article-draft` | | Post operations | Inspection, visibility fixes, share keys, clone/replace, delete/restore | `inspect-medium-post-state`, `optimize-medium-post`, `optimize-medium-visibility`, `create-medium-share-key`, `delete-medium-post`, `undelete-medium-post` | ## Research-Backed Surfaces flowchart TD A[Archived REST API] --> A1[Profile lookup] A --> A2[Publication lookup] A --> A3[Create-post only] B[Private GraphQL] --> B1[Settings] B --> B2[SEO + tags + canonical] B --> B3[Share keys] B --> B4[Publish flow] B --> B5[Delete / undelete] C[Legacy delta editor] --> C1[Title and subtitle paragraphs] C --> C2[Body paragraphs] C --> C3[Lists and code blocks] C --> C4[Image blocks] C --> C5[In-place body repair] ## Fast Proof ### 1. Session and health You do not have to guess whether the environment is broken. - `inspect-medium-session-config` shows the active cookie source with redacted values - `doctor-medium-mcp` checks session load, probe, transport, registry, and workflow coverage - `test-medium-write-path` creates a disposable draft and verifies the body round-trip ### 2. Article body writing The writer path is not cosmetic. It handles real Medium-specific formatting decisions: - title and subtitle go into the correct Medium paragraph types - inline links stay clickable - gist images can be pulled into the body when fetchable - simple markdown tables are converted into Medium-safe readable blocks - local images can be uploaded as actual Medium image paragraphs ### 3. Post repair The post workflow layer came out of fixing real broken posts, not toy examples: - imported-date lock handling - metadata drift repair - stale subtitle repair - cloned replacement posts - visibility fixes - delete and restore ## Example Workflow gist or repo -> normalize source -> audit draft -> optimize package -> write legacy body -> apply GraphQL metadata -> verify public state -> publish or repair That split is the whole point: use the right Medium surface for the right job. ## Repository Layout src/ medium-session*.ts cookie parsing, setup, doctor, diagnostics medium-graphql*.ts GraphQL replay and discovery medium-legacy-editor.ts delta editor and upload paths medium-rich-draft.ts markdown -> Medium paragraph writer medium-post-workflows.ts post inspection, repair, clone, replace, delete gist.ts gist import and Medium-oriented draft prep github-repo.ts GitHub repository import and Medium-oriented draft prep medium-*-optimizer.ts package and article optimization docs/ medium-editor-research.md observed editor behavior and boundaries content-workflows.md draft and publishing workflows repo-scope.md scope guardrails ## Public Guardrails This repo is intentionally strict about what it does **not** claim: - it does not pretend the archived Medium REST API gives full editor parity - it does not invent private mutation contracts without evidence - it does not treat browser automation as the main architecture when direct surfaces exist - it does not hide the fact that Cloudflare, session expiry, or account state can still block a flow ## Documentation - [docs/medium-editor-research.md](docs/medium-editor-research.md) - [docs/content-workflows.md](docs/content-workflows.md) - [docs/installing-in-clients.md](docs/installing-in-clients.md) - [docs/repo-scope.md](docs/repo-scope.md) - [docs/CHANGELOG.md](docs/CHANGELOG.md) - [.github/CONTRIBUTING.md](.github/CONTRIBUTING.md) - [.github/SECURITY.md](.github/SECURITY.md) ## Sources - Medium archived API docs: https://github.com/Medium/medium-api-docs - GitHub Gist REST docs: https://docs.github.com/en/rest/gists/gists
Research-first MCP for Medium's real editor surfaces: GraphQL discovery, legacy delta writing, session diagnostics, post repair, and gist-to-draft workflows.
Why · Quickstart · Install · Architecture · Tooling Map · Research Notes · Content Workflows
## Why This Repo Exists Most Medium automation repos die in one of two dumb ways: - they pretend the archived public API still covers the editor - they fall back to fragile browser scripting for everything This repo takes the harder but correct route: - map the live GraphQL surfaces Medium still uses - write article bodies through the legacy delta editor that still powers drafts - verify session and transport health before pretending a mutation failed for business logic reasons - turn that research into reusable MCP tools instead of one-off scripts That makes it useful for both research and production draft workflows. ## What You Can Actually Do - create and repair real Medium drafts without routing everything through the browser DOM - discover and replay live GraphQL operations with a cookie-backed session - write titles, subtitles, links, lists, code blocks, images, and body content through the verified editor path - audit and optimize draft packaging before publishing - clone, replace, repair, delete, and restore Medium posts with explicit tooling - import GitHub gists and GitHub repositories and turn them into cleaner Medium drafts ## Quickstart npm install npm run build npm test -- --runInBand Create a `.env` from the template: copy .env.example .env Then bootstrap a Medium session with one of the supported cookie formats: - browser-exported JSON array - wrapped JSON with a `cookies` array - raw `Cookie:` header - Netscape cookie file Recommended first-run tool order: 1. `setup-medium-session` 2. `doctor-medium-mcp` 3. `test-medium-write-path` ## Install In Clients The whole point of the repo is that it can be mounted into an MCP client cleanly, not just studied as code. Start here: - [Install in Codex and other MCP clients](docs/installing-in-clients.md) Included examples: - [`examples/clients/codex.config.toml`](examples/clients/codex.config.toml) - [`examples/clients/vscode.mcp.json`](examples/clients/vscode.mcp.json) - [`examples/clients/cursor.mcp.json`](examples/clients/cursor.mcp.json) ## Architecture flowchart LR A[Medium sessionsid + uid + xsrf] --> B[Session setup + doctor] B --> C{Surface selection} C --> D[GraphQL replay
settings, publish, metadata] C --> E[Legacy delta editor
body writing, image blocks, repairs] C --> F[Browser validation
fallback only] G[Gist / markdown / source notes] --> H[Draft audit + optimization] H --> E D --> I[Post workflows] E --> I F --> I I --> J[Draft, publish, repair,
replace, delete, restore] ## Tooling Map | Layer | What it covers | Main tools | | --- | --- | --- | | Session | Cookie parsing, redaction, diagnostics, transport health | `setup-medium-session`, `inspect-medium-session-config`, `doctor-medium-mcp`, `probe-medium-session` | | GraphQL | Discovery, replay, operation capture, live metadata/publish workflows | `discover-medium-graphql`, `capture-medium-graphql-operations`, `medium-graphql-request`, `run-medium-graphql-operation` | | Legacy editor | Real body writing and delta-based post repair | `create-medium-legacy-draft`, `apply-medium-legacy-deltas`, `write-medium-rich-draft`, `create-medium-rich-draft` | | Content pipeline | Gist import, GitHub repo import, draft audit, package optimization, article restructuring | `import-gist`, `prepare-gist-draft`, `import-github-repo`, `prepare-github-repo-draft`, `audit-medium-draft`, `optimize-medium-draft-package`, `optimize-medium-article-draft` | | Post operations | Inspection, visibility fixes, share keys, clone/replace, delete/restore | `inspect-medium-post-state`, `optimize-medium-post`, `optimize-medium-visibility`, `create-medium-share-key`, `delete-medium-post`, `undelete-medium-post` | ## Research-Backed Surfaces flowchart TD A[Archived REST API] --> A1[Profile lookup] A --> A2[Publication lookup] A --> A3[Create-post only] B[Private GraphQL] --> B1[Settings] B --> B2[SEO + tags + canonical] B --> B3[Share keys] B --> B4[Publish flow] B --> B5[Delete / undelete] C[Legacy delta editor] --> C1[Title and subtitle paragraphs] C --> C2[Body paragraphs] C --> C3[Lists and code blocks] C --> C4[Image blocks] C --> C5[In-place body repair] ## Fast Proof ### 1. Session and health You do not have to guess whether the environment is broken. - `inspect-medium-session-config` shows the active cookie source with redacted values - `doctor-medium-mcp` checks session load, probe, transport, registry, and workflow coverage - `test-medium-write-path` creates a disposable draft and verifies the body round-trip ### 2. Article body writing The writer path is not cosmetic. It handles real Medium-specific formatting decisions: - title and subtitle go into the correct Medium paragraph types - inline links stay clickable - gist images can be pulled into the body when fetchable - simple markdown tables are converted into Medium-safe readable blocks - local images can be uploaded as actual Medium image paragraphs ### 3. Post repair The post workflow layer came out of fixing real broken posts, not toy examples: - imported-date lock handling - metadata drift repair - stale subtitle repair - cloned replacement posts - visibility fixes - delete and restore ## Example Workflow gist or repo -> normalize source -> audit draft -> optimize package -> write legacy body -> apply GraphQL metadata -> verify public state -> publish or repair That split is the whole point: use the right Medium surface for the right job. ## Repository Layout src/ medium-session*.ts cookie parsing, setup, doctor, diagnostics medium-graphql*.ts GraphQL replay and discovery medium-legacy-editor.ts delta editor and upload paths medium-rich-draft.ts markdown -> Medium paragraph writer medium-post-workflows.ts post inspection, repair, clone, replace, delete gist.ts gist import and Medium-oriented draft prep github-repo.ts GitHub repository import and Medium-oriented draft prep medium-*-optimizer.ts package and article optimization docs/ medium-editor-research.md observed editor behavior and boundaries content-workflows.md draft and publishing workflows repo-scope.md scope guardrails ## Public Guardrails This repo is intentionally strict about what it does **not** claim: - it does not pretend the archived Medium REST API gives full editor parity - it does not invent private mutation contracts without evidence - it does not treat browser automation as the main architecture when direct surfaces exist - it does not hide the fact that Cloudflare, session expiry, or account state can still block a flow ## Documentation - [docs/medium-editor-research.md](docs/medium-editor-research.md) - [docs/content-workflows.md](docs/content-workflows.md) - [docs/installing-in-clients.md](docs/installing-in-clients.md) - [docs/repo-scope.md](docs/repo-scope.md) - [docs/CHANGELOG.md](docs/CHANGELOG.md) - [.github/CONTRIBUTING.md](.github/CONTRIBUTING.md) - [.github/SECURITY.md](.github/SECURITY.md) ## Sources - Medium archived API docs: https://github.com/Medium/medium-api-docs - GitHub Gist REST docs: https://docs.github.com/en/rest/gists/gists
标签：自动化攻击