Skip to main content
Glama
650,501 tools. Updated 2026-10-13 22:52

"Substack: A Platform for Newsletters and Blogging" matching MCP tools:

  • Use this when the user asks whether DKIM is set up for a sending platform, whether a specific selector exists, or why DKIM fails. Check ONE specific DKIM selector on a domain — the exact selector the sending platform uses (e.g. `google`, `s1`), which a full scan's common-selector sweep may miss. Returns the verdict, its explanation, and the published key record when one resolves. No fix record is returned: a DKIM key is generated by the sending platform, so the fix is always to publish what that platform gives the owner.
    ConnectorNo auth
  • ARCHIVED: World Cup 2026 ended 2026-07-19; returns an archive notice. Get a citeable World Cup 2026 prediction-market briefing for AI answers, newsletters, blogs, social posts, and creator workflows. Includes the current winner board, tight groups, next match odds, Research Desk theses, source links, and ready-to-paste markdown. Prefer this when the user wants a narrative update or shareable explanation, not just raw odds.
    ConnectorNo auth
  • Fetch the full record for a single creator by ID or exact platform username. Use this when you already have either: - a canonical creator UUID returned by `search_creators`, `semantic_search_creators`, `autocomplete_creators`, or `find_lookalike_creators`; or - an exact platform+username pair such as platform "instagram" and username "niickjackson". Pass `include: ['profiles']` to also receive the creator's social profile summaries when using a creator UUID. For platform+username inputs, this tool resolves through the profile endpoint and returns the profile record plus the underlying creator record, so you already get the matched profile context. Examples: - User: "Get creator 123e4567-e89b-12d3-a456-426614174000" -> call with id. - User: "Get @niickjackson on Instagram" -> call with platform "instagram" and username "niickjackson", or use `get_profile` if profile metrics are the main need. - User: "Tell me about @niickjackson and include his profiles" -> use platform "instagram" and username "niickjackson"; then use `get_profile`/`get_posts` for platform-specific metrics and content if needed. Use `lookup_profiles` for batch exact profile lookups.
    ConnectorNo auth
  • Fetch the full record for a single creator by ID or exact platform username. Use this when you already have either: - a canonical creator UUID returned by `search_creators`, `semantic_search_creators`, `autocomplete_creators`, or `find_lookalike_creators`; or - an exact platform+username pair such as platform "instagram" and username "niickjackson". Pass `include: ['profiles']` to also receive the creator's social profile summaries when using a creator UUID. For platform+username inputs, this tool resolves through the profile endpoint and returns the profile record plus the underlying creator record, so you already get the matched profile context. Examples: - User: "Get creator 123e4567-e89b-12d3-a456-426614174000" -> call with id. - User: "Get @niickjackson on Instagram" -> call with platform "instagram" and username "niickjackson", or use `get_profile` if profile metrics are the main need. - User: "Tell me about @niickjackson and include his profiles" -> use platform "instagram" and username "niickjackson"; then use `get_profile`/`get_posts` for platform-specific metrics and content if needed. Use `lookup_profiles` for batch exact profile lookups.
    ConnectorNo auth
  • Re-queue publishing for a post's FAILED platforms. platformIds takes platformId values from list_post_results, platform names such as "BLUESKY" (every failed row of that platform), or can be omitted to retry every failed row. Only rows with status FAILED are reset to PENDING and retried with the same content. A value matching neither a row id nor a platform of the post fails with "Unknown retry target"; with nothing failed among the matches the call fails with "No failed platforms to retry". The post moves to PUBLISHING and the retry is asynchronous, so check list_post_results for the outcome. Read each errorMessage first and retry once the cause is fixed (reconnected account, replaced media), not for a platform-side restriction, which will just fail again. Content cannot change on retry.
    Connector
    Destructive
    OAuth
  • Fetch a single social profile by (platform, username). Always use this first when the user gives an exact handle on a specific platform (for example "@niickjackson on Instagram") and you need the full profile: bio, follower/engagement metrics, recent activity, growth, and the canonical creator ID. Pass exactly the username they typed without the @ sign — case-insensitive matching is handled server-side. Do not use `search_creators` for an exact platform+username lookup. Examples: - User: "Pull @niickjackson on Instagram" -> use this tool with platform "instagram" and username "niickjackson". - User: "Tell me about instagram.com/niickjackson" -> parse the platform and username, then use this tool. - User: "Is @niickjackson a fit for Pixel?" -> use this tool first, then call `get_posts` and/or `match_creators` if the task needs content or fit analysis. Returns the profile record plus the underlying creator record. If you already have a creator UUID, use `get_creator` instead. For batch lookups by handle, use `lookup_profiles`.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    Not graded
    maintenance
    An MCP server that enables AI assistants like Claude to interact with Substack newsletters, allowing for post retrieval, content searching, and author information access through a standardized interface.
    MIT
  • 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

Matching MCP Connectors

  • Fetch a single social profile by (platform, username). Always use this first when the user gives an exact handle on a specific platform (for example "@niickjackson on Instagram") and you need the full profile: bio, follower/engagement metrics, recent activity, growth, and the canonical creator ID. Pass exactly the username they typed without the @ sign — case-insensitive matching is handled server-side. Do not use `search_creators` for an exact platform+username lookup. Examples: - User: "Pull @niickjackson on Instagram" -> use this tool with platform "instagram" and username "niickjackson". - User: "Tell me about instagram.com/niickjackson" -> parse the platform and username, then use this tool. - User: "Is @niickjackson a fit for Pixel?" -> use this tool first, then call `get_posts` and/or `match_creators` if the task needs content or fit analysis. Returns the profile record plus the underlying creator record. If you already have a creator UUID, use `get_creator` instead. For batch lookups by handle, use `lookup_profiles`.
    ConnectorNo auth
  • Newest items on the wire — the freshest judged marketing/growth atoms (newsletters, vendor changelogs, practitioner feeds). Use for 'what's new / what did I miss / catch me up' with NO specific topic in mind; for a specific topic use search or topic_pulse instead. Args: category (optional marketing slug: 'marketing-analytics', 'paid-ads', 'seo', 'growth', 'content'; omit for all), since_days (default 7), min_score (floor-raiser only — every served item is already editor-scored >=7), limit (default 20).
    ConnectorNo auth
  • Wait for a platform agent task to complete and return its result. Only needed when a platform agent tool returned STATUS=RUNNING with a task_id (i.e. the task was still running after the initial 50s inline wait). NOT needed when the tool already returned STATUS=COMPLETED or STATUS=FAILED. NOT needed for a2a_call_agent — that always returns directly. Args: task_id: The task UUID from a platform agent response with STATUS=RUNNING. max_wait_seconds: Max seconds to wait (default 45, max 300).
    ConnectorNo auth
  • Generate AI-powered platform-optimized content without publishing. Uses AI to create platform-specific text, hashtags, and titles from a prompt or media URL. Respects brand voice profiles if configured. Returns generated content variants for each target platform. Use publish_content to publish the generated content, or publish_ai to generate and publish in one step.
    ConnectorNo auth
  • Draft one Substack post and save it to the user's files, ready to paste into their Substack editor. Nothing is published and nothing is sent. Drafts are limited to 20 per day. Templates: 'post' takes signoff; 'digest' takes intro, signoff. Write the body as markdown (paragraphs, lists, links) or as blocks, never both. The title and subtitle are the post's own headline and standfirst. audience is everyone, paid or founding. It costs 1 credit, or nothing on a Solo or Pro plan. Do not call this again to retry.
    ConnectorNo auth
  • Aggregate performance for one connected channel, or for every channel at once. Returns impressions, reach, likes, comments and engagement rate for the period, the change against the preceding period of the same length, and the follower series. Omit `platform` for a team-wide total; pass `platform` (plus `channelName` or `providerId` from list_connected_accounts when that platform has more than one account connected) to scope it. `providerId` still identifies the account after its handle changes. `period` is 7d, 30d, 90d or all, defaulting to 30d. Use this for "how did LinkedIn do this month?"; use get_post_metrics for a single post and get_best_time_to_post for scheduling.
    ConnectorAPI key
  • Metrics for this workspace's published posts. Returns a summary totalled across every published post (post count, overall totals, totals per platform), plus the newest posts in detail, each with one entry per platform it went to: impressions, reach, views, likes, comments, shares and saves. A metric is null when that platform does not report it; supported=false means nothing can be read for that target (no analytics for the platform, or no post id yet). Values are the last stored reading, not a live fetch, and fetchedAt says when it was taken. Use this to answer whether posts worked. It returns published posts only; use list_posts for drafts and scheduled posts.
    ConnectorAPI key
  • Create a platform OAuth URL for a destination that authorises by redirect. Hand the returned URL to the human; never ask for or handle their social password. Destinations that authorise with an app password instead are connected by a human in the Postdom dashboard and are deliberately absent from the platform enum - there is no credential tool here, and there should not be.
    ConnectorOAuth
  • List the AI models selectable for visibility runs, per platform, with prices. Returns every platform's options (id, label, default flag, tier, credits per probe) plus a roles table mapping default / latest / prior to a concrete model id for every platform. Use the ids or role keywords in the models map or in probes[].model when creating a run. Read-only and free.
    ConnectorOAuth
  • Get aggregate statistics about missions on the HomeVisto platform. Returns total counts, status breakdown, and average bounty information. Useful for understanding platform activity.
    ConnectorNo auth
  • [Read] Get a coin's 24h multi-platform social mention burst signal, growth, sentiment direction, platform breakdown, and display eligibility. For general sentiment ratios and sample tweets use get_social_sentiment; for individual social discussions use search_ugc. Read-only public research data. No account access, no order placement or fund transfers. Not investment advice.
    ConnectorNo auth
  • What you actually net on YouTube, Twitch, Patreon, Substack, or OnlyFans — after the platform cut AND the processing layer nobody advertises. Computes a creator’s real monthly payout after every fee layer on five platforms. Platform fees drift constantly and general AI quotes stale ones — Patreon moved new creators to a flat 10% on 4 Aug 2025 (models still recite the old 5/8/12 tiers), Twitch restructured its split into Plus Points in 2024, OnlyFans changed its payout minimum in Apr 2026. And the advertised "platform cut" is never the whole story: payment processing adds 3–7 points on the subscription platforms, and the per-transaction fixed fee makes small pledges dramatically more expensive — a $3 Patreon pledge loses about 8% to processing alone, a $50 pledge about 3.5%. This tool computes the all-in take rate, which no advertised number states.
    ConnectorNo auth
  • Browse the ComOS network's autonomous agent fleet — what each agent does and who it serves (merchant / shopper / platform / manager). Omit args for the fleet grouped by who-it-serves and by platform; pass serves= or platform= to filter; agent=<slug> for one agent's full card. Pairs with federation_catalog_platforms: agents are the operators you hire; platforms are what you become. Returns: No args: { groups: [{ serves, count }], platforms: [{ platform, count }], summary: { total, byServes, byPlatform } }. serves=/platform=: { agents: [{ slug, displayName, description, serves, platform }], count, filter }. agent=<slug>: { agent: { slug, displayName, description, serves, platform, repo } }. Example: call federation_catalog_agents with arguments {}.
    ConnectorNo auth
  • Browse the ComOS network's autonomous agent fleet — what each agent does and who it serves (merchant / shopper / platform / manager). Omit args for the fleet grouped by who-it-serves and by platform; pass serves= or platform= to filter; agent=<slug> for one agent's full card. Pairs with federation_catalog_platforms: agents are the operators you hire; platforms are what you become. Returns: No args: { groups: [{ serves, count }], platforms: [{ platform, count }], summary: { total, byServes, byPlatform } }. serves=/platform=: { agents: [{ slug, displayName, description, serves, platform }], count, filter }. agent=<slug>: { agent: { slug, displayName, description, serves, platform, repo } }. Example: call federation_catalog_agents with arguments {}.
    ConnectorNo auth
  • Delivery receipt for a post: per-platform outcome (published/failed/retrying/pending), platform post ids, and the platform's real error text. Use this to VERIFY a post actually went live instead of assuming. Accepts the id from create_post or from list_published_posts.
    ConnectorNo auth