← Index

substack-ops

io.github.06ketan/substack-ops·v0.3.5·Developer Tools

Substack CLI + 26-tool MCP server. Your IDE drafts replies via propose_reply. No API keys.

Trust verdict · v1 advisory · method
NOT YET SCREENEDno verdict on file

Verdict not yet evaluated for this tool. The semantic screen takes adversarial cases first; coverage rolls out as the corpus expands (15/150 labels to graduation). The deterministic conformance probe is built but has not yet run on the public corpus, so a recorded verdict here is REVIEW or UNVERIFIED, never a clearing ALLOW. Until a verdict is recorded, an agent should treat this tool as not-yet-cleared and fall back to its own checks. Method: the eval, four-state verdict, honest limits.

Own this server? Screen its description →

Environment variables
SUBSTACK_PUBLICATION_URL

Your Substack publication URL (e.g. https://you.substack.com/). Optional if set in ~/.cursor/mcp.json's mcpServers.substack-api.env.

SUBSTACK_USER_ID

Your Substack numeric user id. Optional if set in ~/.cursor/mcp.json.

SUBSTACK_SESSION_TOKEN
secret

Your Substack session cookie value (the s%3A... string). Required for authenticated calls. Easier path: run `substack-ops auth login --browser chrome` and the cookie is auto-grabbed.

SUBSTACK_OPS_MCP_PATH

Override path to the mcp.json file the auth layer reads. Defaults to ~/.cursor/mcp.json.

SUBSTACK_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.

MCP quality score · maturity, not trust · methodology
freshness
24
completeness
20
installability
25
documentation
15
stability
5
Alternatives in Developer Tools