Substack MCP Server
Related Servers
Alternatives to Substack MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to draft, publish, and schedule posts on Substack, bypassing the lack of an official publishing API.134-
- AlicenseNot gradedqualityDmaintenanceEnables managing Substack publications: publish Notes and posts, manage drafts, pull analytics, and read any publication's public feed via MCP.MIT
- 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
- AlicenseAqualityBmaintenanceEnables AI agents to write and publish Substack posts, manage subscribers and analytics, schedule Notes, and research other writers through 65 tools.6553 npm1MIT
- AlicenseNot gradedqualityDmaintenanceCreate, manage, and publish Substack posts with full rich text formatting directly from Claude Desktop or any MCP-compatible client.71 npm26MIT
- 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
TDQS
Scored across 50 tools
Despite the large surface, most tools target distinct resources and actions, and the descriptions clearly separate tricky pairs such as delete_comment vs remove_comment and post vs publication analytics. A few analytics/listing/export tools could still be confused at a glance, so it is not perfect.
Tool names consistently use snake_case verb_noun patterns such as list_posts, create_draft, publish_post, and tag_subscribers. Compound names like get_post_engagement and list_traffic_sources remain predictable and readable.
Fifty tools is excessive for an MCP surface, even for a broad platform like Substack. Many analytics, subscriber, tag, and comment variants are individually justified but collectively impose a high selection cost.
The surface covers the core lifecycle for posts, drafts, scheduling, publishing, subscribers, tags, comments, Notes, DMs, recommendations, search, and analytics. The main gap is that published posts cannot be edited directly without unpublishing first, and sections are list-only rather than fully managed.