substack-mcp
Related Servers
Alternatives to substack-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to search and read Substack newsletter feeds, stage and publish drafts, interact with community comments, and track subscriber and post analytics through local tools and a web dashboard.1MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to draft, publish, and schedule posts on Substack, bypassing the lack of an official publishing API.134-
- AlicenseAqualityFmaintenanceEnables AI tools to programmatically manage Substack content, including creating drafts, publishing posts, and posting to Substack Notes. It supports image uploads, live blogging, and document formatting compatible with Substack's ProseMirror editor.119MIT
- AlicenseNot gradedqualityBmaintenanceEnables managing Substack publications through 27 tools for drafting, publishing, subscriber analytics, comments, Notes, and reader feed via Streamable HTTP.238 npm1MIT
- AlicenseAqualityAmaintenanceEnables AI agents and scripts to manage a self-hosted Substack account through a Chrome session, covering posts and Markdown drafts, scheduling, Notes, comments, subscribers, stats, recommendations, and direct messages via MCP, REST API, or Python.2506PolyForm Noncommercial 1.0.0
- AlicenseNot gradedqualityDmaintenanceEnables programmatic management of Substack content, including creating drafts, publishing posts, and uploading images. It supports specialized features like live blogging and posting to Substack Notes through MCP-compatible AI tools.MIT
TDQS
Scored across 65 tools
Most tools target a distinct resource+action (drafts, notes, subscribers, analytics, tags, templates), and descriptions explicitly clarify near-neighbours like get_post vs get_post_by_id and get_draft vs get_post. A few boundaries blur: get_growth_sources openly duplicates get_analytics' growth_sources report, publish_note vs publish_note_with_link could be one tool, and comment_on_post / get_post_comments / get_comment_thread sit close together. These are workable but not perfectly clean.
Names are uniformly snake_case and overwhelmingly follow verb_noun (create_draft, delete_note, list_subscribers, add_tag_to_post). A handful deviate toward topic verbs or bare nouns — scrape_post, research_creator_posts, compare_publications, upload_image — but the convention is still readable and predictable overall.
65 tools is well past the 25+ 'heavy' threshold and includes acknowledged redundancy (get_growth_sources exists only because it wraps one get_analytics report). The domain is genuinely large, but the surface is bloated enough that selection cost is real.
Coverage is broad and lifecycle-complete in the core areas: draft CRUD plus publish/schedule/unschedule, note publish/schedule/cancel/delete, subscriber list/export/add, analytics, tags, templates, and research/scraping tools. Minor gaps remain — no tag delete/update despite remove_tag_from_post, no subscriber removal, no update/delete for notes beyond delete, and no comment deletion for received comments.