Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Beschreibung vom Entwickler (englisches Original)
Plan, generate, schedule and repurpose posts across every channel, and track what performs.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
MISARPOST_API_KEY, MISARPOST_BASE_URL, AuthorizationAls geheim markierte Werte sind Schlüssel zu deinem Konto. Gib sie nie weiter und füge sie nie in einen Chat ein.
Du brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Diese Adresse braucht einen Schlüssel in einem Header der Anfrage, und das Menü zum Hinzufügen von Connectors kann ihn nicht setzen. Nutze stattdessen Claude Code, Cursor oder VS Code.
Öffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein
{
"mcpServers": {
"misarpost": {
"command": "npx",
"args": [
"-y",
"@misarpost/mcp"
],
"env": {
"MISARPOST_API_KEY": "your-value",
"MISARPOST_BASE_URL": "your-value"
}
}
}
}Führe das in deinem Terminal aus
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/mcpTrag die leeren Werte ein, bevor du ihn startest.
In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"misarpost": {
"url": "https://api.misar.io/post/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"misarpost": {
"command": "npx",
"args": [
"-y",
"@misarpost/mcp"
],
"env": {
"MISARPOST_API_KEY": "your-value",
"MISARPOST_BASE_URL": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"misarpost": {
"type": "http",
"url": "https://api.misar.io/post/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"misarpost": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@misarpost/mcp"
],
"env": {
"MISARPOST_API_KEY": "your-value",
"MISARPOST_BASE_URL": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Diese Adresse braucht einen Schlüssel in einem Header der Anfrage, und das Menü zum Hinzufügen von Connectors kann ihn nicht setzen. Nutze stattdessen Claude Code, Cursor oder VS Code.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
MISARPOST_BASE_URL envAuthorization geheim erforderlich HTTP headerDiese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Die Tool-Liste dieses Servers haben wir noch nicht gelesen; wir prüfen die Endpunkte reihum.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 7. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto Misar-AI bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Noch nicht geprüft; wir prüfen die Endpunkte reihum
Noch nicht geprüft; wir prüfen die Endpunkte reihum
Noch nicht geprüft; wir lesen die Tool-Liste, wenn wir den Endpunkt prüfen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Das musst du eintragen: MISARPOST_API_KEY, Authorization
Beides geht: Installiere ihn auf deinem Computer oder verbinde dich mit der Cloud-Version.
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (3.0.0) kam vor 21 Tagen in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL, also funktionieren auch Apps, die Remote-MCP-Server akzeptieren, zum Beispiel ChatGPT im Entwicklermodus.
In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, Aiterm MCP
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Persistent terminals and one launcher for Claude, Codex, Grok, Cursor, and Antigravity harnesses.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
Plan, generate, schedule and repurpose posts across every connected channel, and track what performs — from any AI assistant.
85 tools · 8 prompts · 6 resources · 8 agent skills
Works with Claude (Desktop, Code, and web), Cursor, VS Code, Windsurf, Cline, Zed, Gemini CLI, ChatGPT, and any other MCP-compatible client — over stdio or Streamable HTTP.
npx -y @smithery/cli install misar/misarpost-mcp --client claude
claude mcp add misarpost -- npx -y @misarpost/mcp@latest
{
"mcpServers": { "misarpost": { "command": "npx", "args": ["-y", "@misarpost/mcp@latest"], "env": { "MISARPOST_API_KEY": "mpk_your_key_here" } } } }
Ready-made configs for every client live in connectors/.
{
"mcpServers": { "misarpost": { "type": "streamable-http", "url": "https://api.misar.io/post/mcp", "headers": { "Authorization": "Bearer mpk_your_key_here" } } } }
Create an API key at https://post.misar.io/dashboard/api-keys (Dashboard → API keys) — it starts with mpk_ — and give it to the server in one of three ways: the MISARPOST_API_KEY environment variable, your MCP client's env block, or { "api_key": "mpk_…" } in ~/.misarpost/config.json.
Self-hosted instances: set MISARPOST_BASE_URL.
| Tool | Description |
|---|---|
list_connections | List the user's active connected social accounts with their account ID, platform and display name. |
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 tags. |
list_account_plugs | Show the plugs (automatic follow-up actions — e.g. |
configure_account_plug | Turn a plug on or off for one connected account and set its configuration, replacing the plug's previous configuration. |
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. |
schedule_post | Schedule a post to ONE connected account at a given time, or publish it immediately with scheduled_at="now". |
cancel_post | Cancel a post that is still pending or queued, so it never publishes. |
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. |
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. |
reply_to_post | Post a public reply/comment on one of the user's ALREADY-PUBLISHED posts, on the platform it was published to. |
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). |
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. |
share_post | Create (or return the existing) public preview link for one of the user's posts. |
unshare_post | Revoke a post's public preview link, so the old link stops working. |
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. |
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. |
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. |
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. |
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. |
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. |
get_contentripple_usage | Show how many ContentRipple repurposes the user has run this month, their monthly limit (null means unlimited), and their plan tier. |
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. |
update_content_variant | Edit a saved ContentRipple variant's text (which marks it edited) and/or set its status. |
schedule_content_variant | Schedule a saved ContentRipple variant (its text plus hashtags) to a connected account of the matching platform at a given time. |
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). |
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. |
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. |
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). |
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. |
generate_plan | For a topic or brief, suggest hook options, the best posting time slots, and trending hashtags per platform. |
research_hashtags | Build a tiered hashtag strategy for a keyword across platforms — broad, mid and niche tags plus each platform's algorithm signals. |
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. |
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. |
get_trends | Get the latest trending hashtags and content hooks for the user's TrendPulse niches, each with a snapshot id. |
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). |
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. |
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. |
send_trend_digest | Email the user their trend digest (top recent trends for their niches) now. |
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. |
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). |
use_trend_platform_content | Turn one platform's generated trend content into a draft post (generating it first if needed). |
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. |
update_post_template | Change a saved post template. |
delete_post_template | Permanently delete a saved post template. |
list_post_tags | List the user's post tags (id, name, colour). |
create_post_tag | Create a post tag with a name and colour, for grouping posts by campaign or theme. |
update_post_tag | Rename and/or recolour a post tag. |
delete_post_tag | Permanently delete a post tag and remove it from every post that carries it. |
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. |
list_video_avatars | List the stock presenter avatars available for AI video generation. |
list_video_voices | List the stock voices available for AI video generation. |
create_video_script | Write a short talking-presenter video script from a post's text. |
| get_persona_job_status | Check a persona extraction jo
Nur der Anfang wird gezeigt; den Rest findest du im Repo