Substack MCP Server
Related Servers
Alternatives to Substack MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server for Substack that lets Claude Code create drafts, upload images, set cover thumbnails, schedule, and publish posts on your Substack publication.1115MIT
- AlicenseNot gradedqualityBmaintenancePrivate MCP server for validating, previewing, creating, and updating Substack newsletter drafts through an MCP-compatible client.149 npm1Apache 2.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
- AlicenseNot gradedqualityAmaintenanceFastMCP server for Substack: publish Notes and posts, pull analytics, manage drafts, bridge Obsidian vault drafts, and generate visual cards.MIT
- AlicenseNot gradedqualityAmaintenanceRead-only MCP server for accessing Substack content including publications, posts, comments, author profiles, recommendations, and Notes feed using your own session token.149 npm4MIT
- AlicenseNot gradedqualityCmaintenanceEnables managing Substack publications: publish Notes and posts, manage drafts, pull analytics, and read any publication's public feed via MCP.MIT
TDQS
Scored across 25 tools
Tools are mostly distinct by resource and action, with a few close pairs like get_draft vs export_draft and plan_draft_update vs preflight_draft. Descriptions clarify the differing purposes (simple content retrieval vs export/conversion review; proposed-change review vs static checks), so an agent can usually select correctly.
All tools follow a consistent snake_case verb_noun pattern (get_*, list_*, create_*, update_draft, add_free_subscriber, upload_image). Even less common verbs like preflight and plan fit the same style, with no mixed conventions or vague names.
At 25 tools, the server is at the heavy end of reasonable. Each tool has some distinct purpose, but overlapping functions such as get_draft vs export_draft and preflight_draft vs plan_draft_update could be consolidated. The breadth makes it feel slightly oversized.
The server covers drafts, posts, notes, subscribers, tags, sections, analytics, and images, which is broad. However, there is no publish or delete for long-form posts, no delete for notes, and no subscriber removal or tag assignment. These are notable lifecycle gaps, even if the server explicitly disclaims some of them.