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.
28 npm
5
MIT
substack-saved-mcp
by toniher
Related Servers
Alternatives to substack-saved-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP 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
- AlicenseAqualityCmaintenanceA 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
- AlicenseAqualityCmaintenanceStandalone 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.214 npm1Apache 2.0
TDQS
A4/5.0
Scored across 18 tools
Disambiguation4/5
The tool set is mostly clearly split by resource (posts vs. notes) and action (save, unsave, list, search, sync, content). The main ambiguity is between content-fetching tools like get_post_content/get_note_content and cached-detail tools like get_saved_post/get_saved_note, which overlap somewhat in returning note/post bodies. The history flag on list/search saved posts adds a secondary mode but remains distinguishable from sync_reading_history.
Naming Consistency4/5
Most tools follow a predictable snake_case verb_noun pattern: save_post, unsave_note, list_saved_posts, search_saved_notes, sync_reading_history. Minor deviations like saved_posts_status and the get_*_content vs get_saved_* distinction keep it from being perfectly uniform, but the convention is still easy to follow.
Tool Count4/5
18 tools is slightly on the heavy side, but the server manages two related resource types (posts and notes) plus sync, search, listing, content retrieval, and status operations. Each tool maps to a fairly specific operation, so the count is reasonable rather than padded.
Completeness5/5
The surface covers the full saved-item lifecycle for both posts and notes: save, unsave, get cached details, fetch content, list, search, and sync. It also includes publication/audience discovery, cache/sync status, and reading-history sync, leaving no obvious dead ends for the stated purpose.
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues