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.1116MIT
- AlicenseNot gradedqualityBmaintenancePrivate MCP server for validating, previewing, creating, and updating Substack newsletter drafts through an MCP-compatible client.454 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.454 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 34 tools
The tool set is broad and mostly well-differentiated, but several near-overlapping read tools could cause misselection: list_public_posts vs list_published_posts, list_subscribers vs search_subscribers, and get_public_post vs get_post. The verbose descriptions clarify the differences, but the names and related payloads leave real ambiguity.
Most tools follow a snake_case verb_noun pattern (list_drafts, get_subscriber, create_note, update_draft), and get/list generally separates single-item vs collection reads. Minor deviations like plan_draft_update vs preflight_draft, create_note_with_link, and get_post_analytics vs get_publication_stats introduce some stylistic inconsistency but not major confusion.
At 34 tools, this server is far beyond the well-scoped 3–15 range and above the threshold where the surface becomes hard to navigate. Many tools are individually justified, but the count reflects a sprawling feature set rather than a focused capability.
Read, draft, and analytics coverage is extensive, but core lifecycle operations are missing: long-form posts cannot be published, scheduled, or deleted, notes cannot be deleted, and subscribers cannot be removed or edited. These are significant gaps that will cause agent workflows to dead-end.