MisarPost MCP Server

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 电脑或云端
• 传输方式: stdio, Streamable HTTP
• 分类: 其他
• 你需要填写：MISARPOST_API_KEY, Authorization

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接
• npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

{
  "mcpServers": {
    "misarpost": {
      "command": "npx",
      "args": [
        "-y",
        "@misarpost/mcp"
      ],
      "env": {
        "MISARPOST_API_KEY": "your-value",
        "MISARPOST_BASE_URL": "your-value"
      }
    }
  }
}

claude mcp add --transport http misarpost https://api.misar.io/post/mcp --header 'Authorization: your-value'

claude mcp add misarpost --env MISARPOST_API_KEY=your-value --env MISARPOST_BASE_URL=your-value -- npx -y @misarpost/mcp

{
  "mcpServers": {
    "misarpost": {
      "url": "https://api.misar.io/post/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

{
  "mcpServers": {
    "misarpost": {
      "command": "npx",
      "args": [
        "-y",
        "@misarpost/mcp"
      ],
      "env": {
        "MISARPOST_API_KEY": "your-value",
        "MISARPOST_BASE_URL": "your-value"
      }
    }
  }
}

{
  "servers": {
    "misarpost": {
      "type": "http",
      "url": "https://api.misar.io/post/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

{
  "servers": {
    "misarpost": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@misarpost/mcp"
      ],
      "env": {
        "MISARPOST_API_KEY": "your-value",
        "MISARPOST_BASE_URL": "your-value"
      }
    }
  }
}

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

• MISARPOST_API_KEY 机密 env
  Your MisarPost API key (mpk_…). Create one at https://post.misar.io/dashboard/api-keys.
• MISARPOST_BASE_URL env
  Override the API base URL. Only needed for self-hosted instances.
• Authorization 机密 必填 HTTP header
  MisarPost API key. Format: Bearer mpk_… — create one at https://post.misar.io/dashboard/api-keys

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月7日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• list_connections

  List the user's active connected social accounts with their account ID, platform and display name. Call this before scheduling: schedule_post needs the connected_account_id, and a post can only go to an account that is connected and active.

• list_publish_options

  Look up the destinations a connected account can publish into — Discord or Slack channels, Pinterest boards, Reddit post flairs, Hashnode or Medium publications, Hashnode tags, Lemmy communities, Listmonk lists or templates, Skool groups, Whop forums, or WordPress categories and

• list_account_plugs

  Show the plugs (automatic follow-up actions — e.g. reposting or resharing a post once it passes a likes or reactions threshold, on X, Bluesky, Threads and LinkedIn) available for one connected account, how each is currently configured and activated, and the account's 20 most rece

• configure_account_plug

  Turn a plug on or off for one connected account and set its configuration, replacing the plug's previous configuration. An activated plug later acts on that account's published posts automatically, in public, without asking again — confirm the exact plug and settings with the use

• list_posts

  List the user's scheduled and published posts, newest-scheduled first, 20 per page, with platform, status, scheduled/published time, post URL, tags and engagement metrics. Filter by status (e.g. queued or pending for what is coming up — the content calendar — or published for wha

• schedule_post

  Schedule a post to ONE connected account at a given time, or publish it immediately with scheduled_at="now". This queues real content for a real audience — show the user the exact text, account and time and get explicit approval first. To post the same content to several accounts

• cancel_post

  Cancel a post that is still pending or queued, so it never publishes. Posts that are already publishing or published cannot be cancelled, and a cancelled post cannot be re-queued — it must be scheduled again. To change a post instead, use update_post. Confirm with the user first.

• get_calendar

  Get every post scheduled between two dates (default: 7 days ago to 30 days ahead), oldest first, with platform, status, time, text, media, first comment and tags — the content calendar view. Optionally only posts with one tag. Needs a plan that includes the content calendar; othe

• update_post

  Edit a post that has not gone out yet (status pending, queued or draft): its text, its scheduled time, its first comment, or its tags. Changing the time moves when it publishes, so confirm the new text and time with the user first. Published posts cannot be edited.

• reply_to_post

  Post a public reply/comment on one of the user's ALREADY-PUBLISHED posts, on the platform it was published to. It goes live immediately and cannot be recalled from here. Show the user the exact text and get their explicit approval before calling. Not every platform supports repli

• revert_post

  Delete an ALREADY-PUBLISHED post from the platform it went out on (unlike cancel_post, which only stops a post that has not published yet). This removes it from the user's live profile and cannot be undone. Get the user's explicit approval for this exact post first. The response

• revert_post_batch

  "Delete everywhere": delete every published post from one batch (one compose or repurpose action sent to several accounts) from all of its platforms. Each platform is attempted separately and reported separately; some platforms (e.g. TikTok) have no delete API and need manual cle

• share_post

  Create (or return the existing) public preview link for one of the user's posts. Anyone with the link can view the post without signing in, so get the user's explicit approval before sharing. Revoke it with unshare_post.

• unshare_post

  Revoke a post's public preview link, so the old link stops working. Safe to call when no link exists.

• list_drafts

  List up to 50 draft post variants awaiting review (status draft or pending_review), newest first — including AI-generated drafts from generate_posts — with platform, caption, hashtags, tone and source.

• review_drafts

  Approve or reject several drafts at once by ID. Approving does NOT schedule or publish anything — use schedule_post for that. Rejected drafts drop out of list_drafts. Returns how many drafts were updated.

• get_stats

  Get the account overview: connected accounts, posts queued, published this week and this month, drafts waiting, the last published post, the top performing post of the month, and the average engagement rate (null when no metrics exist yet).

• get_analytics_trends

  Get per-channel daily trends for the last 7, 30 or 90 days: posts published and failed, engagement and impressions, totals, and the change against the previous period. Each channel's metric field says whether real engagement data exists for it (engagement) or only publish volume

• get_growth_overview

  Get the Growth Hub overview for the last 7, 30 or 90 days: per-platform engagement trend lines, the weakest-performing platforms (bottlenecks), which post formats perform best, and which platforms have real trend data behind their suggestions. Requires the Empire plan; on other p

• list_growth_opportunities

  List rising trends worth posting about now, limited to the user's niches and to platforms they have connected, each with the hashtag, its growth, and a posting suggestion. Returns an empty list — never an invented one — when no real signal exists. Requires the Empire plan; on oth

• list_growth_playbooks

  Get per-platform growth playbooks for the user's connected platforms — cadence, format, timing and anti-spam guidance compiled from each platform's official creator documentation, with source links. Requires the Empire plan; on other plans it returns an upgrade message.

• get_next_growth_opportunity

  Get the single best next content opportunity for the user's connected platforms and niches — a compact version of list_growth_opportunities. Returns `{ opportunity: null }` rather than an invented one when there is no real signal. Requires the Empire plan; on other plans it retur

• get_contentripple_usage

  Show how many ContentRipple repurposes the user has run this month, their monthly limit (null means unlimited), and their plan tier. Check before a large repurposing run so it does not stop halfway.

• repurpose_content

  Turn one source — a URL, pasted text or markdown, or an RSS item — into channel-native variants such as an X thread, LinkedIn post or carousel, Instagram caption or reel script, newsletter, or YouTube description. Fetches the URL, extracts the core message, writes each variant wi

• update_content_variant

  Edit a saved ContentRipple variant's text (which marks it edited) and/or set its status. Use the variant id returned by repurpose_content. Publishes nothing.

• schedule_content_variant

  Schedule a saved ContentRipple variant (its text plus hashtags) to a connected account of the matching platform at a given time. Only these formats can be published: twitter_thread, linkedin_post, linkedin_carousel, instagram_caption, instagram_reel_script, threads_post, mastodon

• fetch_content_feed

  Read an RSS or Atom feed and return its entries, so the user can pick one to repurpose with repurpose_content (source_type rss). Nothing is saved.

• parse_content_source

  Extract the core message, key points and structure from a URL, pasted text (50-20,000 characters) or Markdown, without generating any variants — a preview of what repurpose_content would work from. Counts against the monthly repurpose limit and uses one AI text action, so prefer

• list_repurpose_history

  List past ContentRipple repurposes, newest first: each source (type, URL, title, core message) with its variants and, for variants that were scheduled, the post's status, URL and engagement.

• delete_repurpose_source

  Delete one repurposed source and its variants from ContentRipple history. Posts already scheduled or published from it are not touched. This cannot be undone — confirm with the user first.

• generate_posts

  Write AI post variants about a topic for one or more platforms — up to 5 per platform — and save them as drafts (visible in list_drafts). Nothing is scheduled or published. Each call counts against the plan's monthly AI generation allowance.

• enhance_topic

  Rewrite a raw topic or idea into a structured content brief: a sharper topic, suggested tone, content angles and key messages for the chosen platforms. Saves nothing; counts against the monthly AI allowance. Feed the result to generate_plan or generate_posts.

• generate_plan

  For a topic or brief, suggest hook options, the best posting time slots, and trending hashtags per platform. Saves nothing and schedules nothing; counts against the monthly AI allowance.

• research_hashtags

  Build a tiered hashtag strategy for a keyword across platforms — broad, mid and niche tags plus each platform's algorithm signals. Saves nothing; counts against the monthly AI allowance.

• get_optimization_insights

  Analyse the last 30 days of post metrics with AI and return the best time of day, best tone, top hashtags, prompt suggestions and per-platform insights. Changes nothing, but each call counts against the monthly AI allowance.

• generate_image

  Generate an image for a post from a text prompt, sized for the platform (16:9 for X, LinkedIn and YouTube, square for Instagram and Threads, 9:16 for TikTok), and store it in the user's media. Returns its URL to attach to a post. Uses one AI image action from the plan's quota. No

• get_trends

  Get the latest trending hashtags and content hooks for the user's TrendPulse niches, each with a snapshot id. Returns cached results under two hours old, or refreshes them live from the trend sources.

• queue_trend_drafts

  Turn 1–3 trend snapshots (from get_trends) into draft posts — one per snapshot for each platform the user has connected — saved to the draft queue (list_drafts). Nothing is scheduled or published.

• schedule_trend_posts

  Publish posts about 1–3 trend snapshots to the given connected accounts, scheduled five minutes from now — one post per content hook per account, written from the trend's hooks. This puts real content in front of a real audience almost immediately and the user does not see the te

• refresh_trends

  Force a fresh fetch of trending hashtags from every trend source for the user's niches and store new snapshots, instead of waiting for the scheduled refresh. Needs a plan that includes manual refresh; otherwise it returns an upgrade message. Use get_trends afterwards to read them

• send_trend_digest

  Email the user their trend digest (top recent trends for their niches) now. It always goes to the account owner's own address — never anyone else. Returns `skipped` when the digest is turned off or there are no recent trends.

• get_trend_hooks

  Get the content hooks (opening lines and angles) for one trend snapshot — snapshot ids come from get_trends.

• get_trend_platform_content

  Get the per-platform content already generated for one trend snapshot — hashtags, plus title/description for YouTube and title/subtitle for Medium. Empty until generate_trend_platform_content has run for it.

• generate_trend_platform_content

  Generate per-platform content (hashtags, and titles where a platform needs them) for one trend snapshot, for the platforms asked (default: all seven). Regenerating replaces the earlier content for those platforms. Nothing is posted — turn one into a draft with use_trend_platform_

• use_trend_platform_content

  Turn one platform's generated trend content into a draft post (generating it first if needed). The draft lands in the review queue (list_drafts) — nothing is published or scheduled.

• get_trend_performance

  Show how the user's trend-sourced posts actually performed: each TrendPulse draft (last 100) joined to whether it was scheduled or published and its likes, comments, reposts, impressions and reach.

• list_post_templates

  List the user's saved post templates, most recently updated first — reusable composer states with text, per-platform overrides, target accounts, platform settings, media and first comment.

• get_post_template

  Get one saved post template in full, by id — to reuse its text, accounts and settings in schedule_post.

• create_post_template

  Save a reusable post template: default text, optional per-platform text, target accounts, platform settings, media and first comment. Saving publishes nothing.

• update_post_template

  Change a saved post template. Only the fields passed are changed, and each one passed replaces the stored value entirely (e.g. account_ids replaces the whole list).

• delete_post_template

  Permanently delete a saved post template. Posts already scheduled from it are not affected. Confirm with the user first.

• list_post_tags

  List the user's post tags (id, name, colour). Tag ids filter list_posts and get_calendar and are applied with schedule_post or update_post.

• create_post_tag

  Create a post tag with a name and colour, for grouping posts by campaign or theme. Names must be unique per user.

• update_post_tag

  Rename and/or recolour a post tag. Posts keep the tag.

• delete_post_tag

  Permanently delete a post tag and remove it from every post that carries it. The posts themselves are not affected. Confirm with the user first.

• list_media

  List the user's uploaded media library, newest first, 24 per page, with each file's public URL — usable directly in schedule_post's media_urls.

• delete_media

  Permanently delete a file from the media library and storage. Posts that already include its URL keep their own copy of the URL, but the file behind it is gone. Confirm with the user first.

• list_video_avatars

  List the stock presenter avatars available for AI video generation. Pass an avatar's id to generate_video.

• list_video_voices

  List the stock voices available for AI video generation. Pass a voice's id to generate_video.

• create_video_script

  Write a short talking-presenter video script from a post's text. Saves nothing; counts against the monthly AI allowance. Show the script to the user before generate_video.

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

• ✓ 通过

  作者与仓库一致

  注册名称已通过 GitHub 账户 Misar-AI 验证，该账户拥有此仓库

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 1470 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 60 个工具描述，未发现针对 AI 的隐藏指令

与“其他”中的其他服务器比较i

• 星标数多于此分类中其他 18433 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 18433 个服务器的 67% 更新
• 基础检查结果等于或优于此分类中其他 18433 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

npx -y @smithery/cli install misar/misarpost-mcp --client claude

claude mcp add misarpost -- npx -y @misarpost/mcp@latest

{

{