Skip to main content
Glama
jakewlittle-cs

substack-insights-mcp

by jakewlittle-cs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to substack-insights-mcp

No user-submitted related servers found.

    Related Servers

    • substack-saved-mcp

      toniher
      A
      license
      A
      quality
      A
      maintenance
      A local MCP server for managing saved Substack posts. Enables offline reading, searching, bookmarking, and unbookmarking of Substack content via CLI or MCP clients.
      17
      MIT

    • substack-vault

      flap4fun
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP 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

    • substack-mcp

      ryanrodrigues25200525-svg
      A
      license
      Not graded
      quality
      A
      maintenance
      Read-only MCP server for accessing Substack content including publications, posts, comments, author profiles, recommendations, and Notes feed using your own session token.
      239 npm
      4
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: listing vs retrieving posts, managing versions, tracking metrics, comparing posts, analyzing patterns, and handling drafts. Even potentially similar tools like get_post and list_post_versions are clearly differentiated by latest vs full history.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (list_posts, get_post, record_metric_snapshot, create_local_draft). The only outlier is connection_status, which is a noun phrase rather than a verb-oriented name, making it slightly inconsistent.

    Tool Count5/5

    12 tools is well within the ideal range for a focused server. Each tool earns its place by covering a distinct aspect of the publication insight workflow: syncing, querying, versioning, auditing, metrics, analysis, and drafts.

    Completeness4/5

    The toolset covers the full lifecycle for content ingestion (sync), retrieval (list/get), version history, audit, metric recording/analysis, and draft management. Minor gaps like explicit list/delete for drafts are mitigated by the immutable ledger design and list_posts coverage, but a dedicated draft listing would improve completeness.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources