substack-ops

substack-ops

Standalone Substack CLI + 26-tool MCP server for Cursor MCP, Claude MCP, OpenCode MCP, and any stdio MCP host. Your IDE drafts the replies. Zero AI API keys.

Site → [substack-ops.chavan.in](https://substack-ops.chavan.in) · Source → [06ketan/substack-ops](https://github.com/06ketan/substack-ops) · Glama → [mcp/servers/06ketan/substack-ops](https://glama.ai/mcp/servers/06ketan/substack-ops)

Posts, notes, comments, replies, reactions, restacks, recommendations, search, profiles, feeds, automations, MCP server, Textual TUI. One Python install, one binary, MIT licensed.

TL;DR — MCP-native (no API key, one command)

uvx substack-ops mcp install cursor          # or claude-desktop, claude-code, opencode, print

Restart your host. Then in chat:

"list unanswered comments on post 193866852"

"draft a warm reply to comment 12345"

"post that draft"

Your host's LLM (Cursor's, Claude's) does the drafting via the propose_reply / confirm_reply tools. No ANTHROPIC_API_KEY / OPENAI_API_KEY needed.

Wrong install?

This project is `substack-ops` on [PyPI](https://pypi.org/project/substack-ops/) — install with `uv` / `uvx`, not unrelated `npx` packages that appear when searching “Substack MCP”. Canonical listing: [Glama — 06ketan/substack-ops](https://glama.ai/mcp/servers/06ketan/substack-ops).

Works with (MCP)

These rows help discovery (search keywords); confirm each host’s current MCP docs before upgrading.

Open source–oriented hosts

Large commercial stacks

OpenCode (copy-paste)

Auto-install:

uvx substack-ops mcp install opencode

Manual (~/.config/opencode/opencode.json):

{

"mcp": { "substack-ops": { "type": "local", "command": ["uvx", "substack-ops", "mcp", "serve"], "enabled": true } } }

Optional version pin: use ["uvx", "substack-ops==0.3.5", "mcp", "serve"] (replace with current PyPI release).

Setup (dev / from source)

git clone https://github.com/06ketan/substack-ops && cd substack-ops

uv sync uv sync --extra mcp # mcp SDK for the MCP server (recommended) uv sync --extra tui # textual for the TUI uv sync --extra chrome # pycryptodome + keyring for Chrome cookie auto-grab

Auth defaults to ~/.cursor/mcp.json's mcpServers.substack-api.env. Override with env or .env. Or use one of the auth flows in auth login / auth setup.

uv run substack-ops auth verify

uv run substack-ops quickstart # 20-step tour

Command surface

Grouped by intent. Every write defaults to --dry-run; flip with --no-dry-run (and --yes-i-mean-it for the irreversible ones). All writes land in .cache/audit.jsonl and are dedup-checked against .cache/actions.db.

Auth (4)

Read — Posts (8)

Read — Notes (5)

Read + Write — Comments (5)

Reply engine (6)

Read — Discovery (8)

Automations (3)

Operations + safety (3)

MCP server (3)

Other (1)

Multi-publication

Every read command accepts --pub . Defaults to your own publication.

substack-ops posts list --pub stratechery --limit 5

substack-ops posts search "ai" --pub stratechery substack-ops recommendations list --pub stratechery

Reply modes

After every live note-reply the engine re-fetches the new comment and asserts ancestor_path is non-empty. If empty, the audit row's result_status is flipped to "orphaned" (the M2 bug where parent_comment_id was silently dropped — now caught).

Automations

Built-in presets (auto presets):

1. like-back — when someone reacts to your note, react to their latest note.
2. auto-reply — same trigger, but post a templated thank-you.
3. auto-restack — when a watchlist handle posts a new note, restack it.
4. follow-back — when someone follows you, follow them back.

Custom YAML rules under ~/.config/substack-ops/auto/*.yaml. Loop with auto daemon --interval 60.

MCP server

substack-ops mcp install opencode          # auto-add to ~/.config/opencode/opencode.json

substack-ops mcp install cursor # auto-add to ~/.cursor/mcp.json substack-ops mcp install claude-desktop # auto-add to claude_desktop_config.json substack-ops mcp install claude-code