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 gradedqualityBmaintenanceEnables AI agents to draft, publish, and schedule posts on Substack, bypassing the lack of an official publishing API.135-
- 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.239 npm2MIT
- 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
- AlicenseBqualityNot gradedmaintenanceEnables interaction with Substack publications through natural conversation, allowing users to create posts with cover images, publish notes, manage content, and retrieve profile information.82 npm-
TDQS
Scored across 65 tools
Most tools target a specific resource and the descriptions are unusually explicit about boundaries, but a handful of pairs overlap in purpose: get_growth_sources duplicates the growth_sources report inside get_analytics, and the many post-reading tools (get_post, get_post_by_id, scrape_post, get_reader_post) require careful reading to pick correctly. This is more than a one-off confusion, so it is not a 4, but the detailed docs keep it from being worse.
The set overwhelmingly follows a snake_case verb_noun pattern (create_draft, list_subscribers, delete_note), which is predictable across drafts, posts, notes, and subscribers. Minor deviations like cancel_scheduled_note vs unschedule_draft, research_creator_posts, and compare_publications break the pattern slightly, so it is not a perfect 5.
65 tools is a very heavy surface for an agent to hold, and not every tool earns independent status: get_growth_sources duplicates a get_analytics report, publish_note_with_link is a thin variant of publish_note, and multiple post readers overlap. Even for a broad Substack platform server, this exceeds a manageable count.
The draft lifecycle is complete (create/read/update/delete/schedule/publish), and analytics, notes, tags, comments, and research are well covered. However, there is no way to edit or delete an already-published post, no subscriber removal/updating beyond adding, and no section/tag management beyond listing and creating, leaving some lifecycle gaps.