A
licenseNot graded
qualityD
maintenanceMCP server for Substack that enables reading articles, comments, feed, and subscriptions from AI clients like Cursor and Claude, with optional authentication for paid content.
19 npm
3
MIT
substack-saved-mcp
by toniher
Related Servers
Alternatives to substack-saved-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server that ingests Substack newsletters from Zoho Mail, archives them locally, and provides search and cross-author topic analysis tools for reading and comparing articles.MIT
- AlicenseBqualityDmaintenanceAn MCP server that gives Copilot access to Substack posts from your authenticated reader account, including paid subscriptions, enabling daily summary generation by syncing, caching, and summarizing posts.13MIT
- AlicenseAqualityBmaintenanceA credential-free MCP server that turns a Substack publication's public RSS archive and official analytics snapshots into a durable, queryable local SQLite ledger. It provides 12 MCP tools for browsing posts, tracking versions, recording metric snapshots, and analyzing content patterns.12Apache 2.0
- AlicenseAqualityBmaintenanceStandalone Substack CLI + 26-tool MCP server. Your IDE drafts the replies. Zero AI API keys.261MIT
- AlicenseNot gradedqualityDmaintenancePrivate MCP server for validating, previewing, creating, and updating Substack newsletter drafts through an MCP-compatible client.403 npm1Apache 2.0
TDQS
A3.9/5.0
Scored across 17 tools
Disambiguation4/5
Posts and notes have parallel tool sets, and most operations are distinct (list, search, sync, save, unsave). However, get_saved_post vs get_post_content and get_saved_note vs get_note_content overlap in retrieving post/note data, which could cause misselection.
Naming Consistency3/5
Most tools use a verb_noun pattern (list_saved_posts, save_post, sync_saved_notes), but the 'saved_' prefix is applied inconsistently: save_post/unsave_post/get_post_content omit it while list_saved_posts/get_saved_post include it. saved_posts_status also breaks the verb_noun pattern.
Tool Count4/5
17 tools cover two entity types (posts, notes) with parallel lifecycle operations plus three shared utilities; each tool has a clear role. Slightly heavy but reasonable for the domain.
Completeness4/5
Core lifecycle for saved posts and notes is covered: list, get, search, save, unsave, sync, and content fetch. Minor gap: no tool to manually update read state/progress despite read_state filters, and saved_posts_status is named for posts only.
Maintenance
ActivityMaintained
ResponsivenessNo issues