Lass KI-Agenten Social-Media-Posts planen, veröffentlichen und analysieren sowie Brand Analytics über die Markaestro API verwalten.
Auch bekannt als markaestro/markaestro-agents, mcp, @markaestro/mcp
- Stars
- 0
- Tools
- 18
- Downloads, 30 Tage
- —
- Neueste Version
- 0.5.0
- Letzter Commit
- 13. Nov. 2026
- Lizenz
- MIT
Was ist Markaestro MCP?
Lass KI-Agenten Social-Media-Posts planen, veröffentlichen und analysieren sowie Brand Analytics über die Markaestro API verwalten. Er stellt 18 Tools bereit, etwa list_products, list_destinations, get_brand_profile.
Zusammenfassung generiert aus dem README des Projekts
Über Markaestro MCP server
Markaestro bietet einen MCP server, der es KI-Agenten ermöglicht, Social-Media-Workflows über eine einzige Schnittstelle zu verwalten. Entwickler können Clients wie Claude, Cursor oder ChatGPT anbinden, um Brand-Content zu planen, zu veröffentlichen und zu überprüfen. Der Server unterstützt sowohl gehostete Verbindungen via HTTP unter Verwendung von OAuth 2.1 als auch lokale Installationen via stdio. Lokale Setups erlauben es dem upload_media Tool, direkt auf Dateien auf deinem Rechner zuzugreifen, während die gehostete Version keine Installation erfordert und einen browserbasierten Login-Prozess nutzt.
User können Inhalte für eine einzelne Brand oder einen gesamten Workspace verwalten, abhängig von den Berechtigungen des API-Keys. Das Toolset umfasst Funktionen zum Erstellen von Einzel- oder Bulk-Posts, zur Verwaltung von Media-Assets und zur Überwachung der Performance durch detaillierte Analytics. Zudem gibt es Evergreen-Tools für die Handhabung von wiederkehrenden Inhalten. Um die Sicherheit zu gewährleisten, folgt der Server einem Draft-first-Ansatz, bei dem das Veröffentlichen explizite Befehle erfordert. Agenten sind zudem daran gehindert, Abrechnungen, Team-Einstellungen oder bereits veröffentlichte Posts zu ändern oder zu löschen.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
So installierst du Markaestro MCP
Formate geprüft am 10. Nov. 2026Zu Cursor hinzufügenZu Goose hinzufügenMarkaestro MCP in Claude Code installieren
$ claude mcp add --env 'MARKAESTRO_API_KEY=<YOUR_MARKAESTRO_API_KEY>' mcp -- npx -y @markaestro/mcpMarkaestro MCP in Cursor installieren
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@markaestro/mcp"
],
"env": {
"MARKAESTRO_API_KEY": "<YOUR_MARKAESTRO_API_KEY>"
}
}
}
}Markaestro MCP in VS Code installieren
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@markaestro/mcp"
],
"env": {
"MARKAESTRO_API_KEY": "<YOUR_MARKAESTRO_API_KEY>"
}
}
}
}Markaestro MCP in VS Code CLI installieren
$ code --add-mcp '{"name":"mcp","type":"stdio","command":"npx","args":["-y","@markaestro/mcp"],"env":{"MARKAESTRO_API_KEY":"<YOUR_MARKAESTRO_API_KEY>"}}'Markaestro MCP in Claude Desktop installieren
claude_desktop_config.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@markaestro/mcp"
],
"env": {
"MARKAESTRO_API_KEY": "<YOUR_MARKAESTRO_API_KEY>"
}
}
}
}Markaestro MCP in Codex installieren
$ codex mcp add mcp --env 'MARKAESTRO_API_KEY=<YOUR_MARKAESTRO_API_KEY>' -- npx -y @markaestro/mcpMarkaestro MCP in Codex config.toml installieren
~/.codex/config.toml
[mcp_servers.mcp] command = "npx" args = ["-y", "@markaestro/mcp"] [mcp_servers.mcp.env] MARKAESTRO_API_KEY = "<YOUR_MARKAESTRO_API_KEY>"
Markaestro MCP in Gemini CLI installieren
$ gemini mcp add -s user -e 'MARKAESTRO_API_KEY=<YOUR_MARKAESTRO_API_KEY>' mcp npx -- -y @markaestro/mcpMarkaestro MCP in Gemini settings.json installieren
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@markaestro/mcp"
],
"env": {
"MARKAESTRO_API_KEY": "<YOUR_MARKAESTRO_API_KEY>"
}
}
}
}Markaestro MCP tools 18
Erkannt aus dem READMElist_productslist_destinationsget_brand_profilecreate_postupdate_postpublish_postmark_post_posteddelete_postbulk_postscreate_postsupload_mediaget_analytics
| list_products | — | |
| list_destinations | — | |
| get_brand_profile | — | |
| create_post | — | |
| update_post | — | |
| publish_post | — | |
| mark_post_posted | — | |
| delete_post | — | |
| bulk_posts | — | |
| create_posts | — | |
| upload_media | — | |
| get_analytics | — |
Alle 18 Tools anzeigenWeniger Tools anzeigen
list_post_analyticsget_post_analytics_historyrefresh_analyticssuggest_post_timesget_channel_rulesget_tiktok_posting_options
| list_post_analytics | — | |
| get_post_analytics_history | — | |
| refresh_analytics | — | |
| suggest_post_times | — | |
| get_channel_rules | — | |
| get_tiktok_posting_options | — |
Konfiguration
MARKAESTRO_API_KEYErforderlichSecretWorkspace API key (mk_live_ or mk_test_) from Settings, API Access. Covers one brand or all brands in the workspace.
MARKAESTRO_READ_ONLYSet to 1 to register only the reading tools.
| Name | Beschreibung | Typ |
|---|---|---|
| MARKAESTRO_API_KEY | Workspace API key (mk_live_ or mk_test_) from Settings, API Access. Covers one brand or all brands in the workspace. | ErforderlichSecret |
| MARKAESTRO_READ_ONLY | Set to 1 to register only the reading tools. |
Automatisierte Checks
Geluften am 12. Nov. 2026Vollständiger Bericht →Unsere automatisierten Checks bestanden. Das ist kein Security-Audit: Lies den Code und gib dem Server nur den minimal notwendigen Zugriff. Wie die Checks funktionieren
- Source Repository verknüpft und erreichbarBestanden
- Open Source Lizenz (OSI)Bestanden
- Commit oder Release im letzten JahrBestanden
- Package-Name ähnelt keinem populären PackageBestanden
- Remote Endpoint nutzt HTTPSBestanden
- Destruktive Tools sind markiertNicht geprüft
- Keine versteckten Anweisungen an das ModellBestanden
- Keine kritischen Advisories im Paket oder seinen AbhängigkeitenBestanden
README
Auf GitHub ansehen@markaestro/mcp
A Model Context Protocol server that lets AI
agents (Claude Code, Claude, Cursor, ChatGPT, Grok, Grok Bot, OpenClaw, Hermes,
and any other MCP client) schedule, publish, and review Markaestro posts
through the public API. Exact connection steps per client are on
https://markaestro.com/developers/agents (?client=cursor, chatgpt, grok,
grok-bot, openclaw, hermes, or headless opens that tab).
Every key covers either one brand or every brand in its workspace, chosen
when the key is created or at the sign-in consent. A single-brand key works on
that brand alone. An all-brands key sees every brand: list_products returns
them all, and the agent passes productId to create_post, create_posts,
list_posts, and create_evergreen_queue, and to the analytics tools to
report on one brand instead of the whole workspace.
Tools
| Tool | What it does |
|---|---|
list_products |
The brands this key can act on (one, or all in the workspace) and their connected channels |
list_destinations |
Publishable destinations of the brand (pages, accounts) with ids |
get_brand_profile |
A brand's description, voice, and visual identity (read-only) |
list_posts, get_post |
Read posts by status, page through with cursor |
create_post |
Save a draft, or schedule when scheduledAt is set |
update_post |
Edit a draft or scheduled post: caption, media, one channel's settings, or its time |
publish_post |
Queue an immediate publish; returns a job run |
mark_post_posted |
Record that a person posted a manual-reminder or TikTok-inbox post |
delete_post |
Delete a draft, or cancel a post before it reaches any platform; published posts are refused |
bulk_posts |
Reschedule or restatus up to 25 posts |
create_posts |
Up to 25 posts in one call, per-item results |
upload_media |
Upload from a file path, URL, or data URL; returns the asset id |
list_media, get_media |
Uploaded assets, processing state, reference counts |
get_analytics |
Brand performance over a window: totals, channels, daily series, top posts, heatmap, insights. Covers posts published through Markaestro and posts published directly on the platform |
list_post_analytics |
Every post in the window with its latest metrics and source, sortable by views, reach, engagements, or engagement rate |
get_post_analytics_history |
The 1h to 90d metric snapshots of one post, with growth between stages |
refresh_analytics |
Pull live metrics from the platforms now (a few calls a minute) |
suggest_post_times |
The brand's best posting windows, learned from its own history |
get_job_run, list_job_runs |
Follow a publish to succeeded or failed |
get_channel_rules |
Per-channel media, caption, and delivery-mode rules |
get_tiktok_posting_options |
The TikTok creator's live privacy levels and interaction options, needed for a Direct Post |
The Evergreen tools (preview_, create_, get_, list_, update_,
activate_, pause_, and resume_evergreen_queue, list_evergreen_runs,
get_evergreen_analytics) manage proven recurring content.
Agents manage social media and nothing else: account settings, billing,
team, API keys, webhooks, and channel connections are not exposed, and no
tool deletes a published post, takes one down from a platform, or archives
an Evergreen queue. Those stay with the user in Markaestro. The same rule
holds at the REST layer for a key issued through the agent sign-in: it
cannot remove a published post, take one down from a platform, or manage
webhooks (FORBIDDEN_AGENT_CONNECTION). A key a person mints in Settings
keeps the full REST surface its scopes allow.
Also served: the markaestro://channel-rules resource and a schedule_post
prompt that walks an agent through a safe scheduling flow.
Posting is draft-first. create_post without scheduledAt never publishes;
publish_post is the only tool that publishes now, and its description tells
the agent to confirm with the user first.
Two ways to connect
Hosted (nothing to install, nothing to paste). Markaestro serves the
same tools over Streamable HTTP at https://markaestro.com/api/public/v1/mcp.
Add it with no credentials and the first tool call opens the browser: sign
in, pick the workspace and brand, click Allow. The client receives an API key
bound to that brand and refreshes it on its own.
claude mcp add --transport http markaestro https://markaestro.com/api/public/v1/mcp
This is standard OAuth 2.1 (PKCE, dynamic client registration, discovery at
/.well-known/oauth-protected-resource and
/.well-known/oauth-authorization-server), so claude.ai, Cursor, and other
MCP clients connect the same way. Connected agents are listed and revoked in
Settings, API.
For headless or CI use, pass a workspace API key as a bearer header instead:
claude mcp add --transport http markaestro https://markaestro.com/api/public/v1/mcp \
--header "Authorization: Bearer mk_live_..."
{
"mcpServers": {
"markaestro": {
"type": "http",
"url": "https://markaestro.com/api/public/v1/mcp",
"headers": { "Authorization": "Bearer mk_live_..." }
}
}
}
Send x-markaestro-read-only: 1 as an extra header to get only the reading
tools.
Local package. Run the server on your machine over stdio, which also
lets upload_media read local files:
Setup
- Create an API key in Markaestro under Settings > API Access. Pick the brand,
the scopes the agent needs (
products.read,posts.read,posts.write,media.write, andposts.publishif it may publish), and prefer a test key while you evaluate. - Give the key to the server through
MARKAESTRO_API_KEY.
Claude Code
claude mcp add markaestro -e MARKAESTRO_API_KEY=mk_live_... -- npx -y @markaestro/mcp
Claude Desktop, Cursor, and other JSON configs
{
"mcpServers": {
"markaestro": {
"command": "npx",
"args": ["-y", "@markaestro/mcp"],
"env": { "MARKAESTRO_API_KEY": "mk_live_..." }
}
}
}
Environment
| Variable | Required | Default |
|---|---|---|
MARKAESTRO_API_KEY |
yes | n/a |
MARKAESTRO_BASE_URL |
no | https://markaestro.com |
MARKAESTRO_READ_ONLY |
no | unset; 1 registers only reading tools |
What the server does for you
- Sends an
Idempotency-Keyon every mutation, minted once per call, so a retried request replays instead of double-posting. - Retries
429and transient5xxresponses using the server'sRetry-After. - Runs the three-step direct media upload (session,
PUTto storage, finalize) and never sends the API key to the storage URL. - Returns API failures as tool errors with the stable error
code, any per-channelissues, and a hint about what to change.
Claude Code plugin
The skill and the hosted server ship together as a plugin:
claude plugin marketplace add markaestro/markaestro-agents
claude plugin install markaestro@markaestro
Deploying
Maintainers: the full release runbook (every surface, the version files, and the exact
commands) is docs/operations/mcp-release.md in the Markaestro app repository. Summary:
| Surface | How it ships |
|---|---|
Hosted MCP (/api/public/v1/mcp) |
Part of the Next.js app; deploys on push to main like every route |
@markaestro/mcp on npm |
cd mcp && npm version <x.y.z> && npm publish (public scoped package; prepublishOnly builds). Bump src/version.ts with it |
| Plugin and skill | Mirrored to the public repo markaestro/markaestro-agents with node scripts/sync-agents-repo.mjs <clone>, then pushed there; claude plugin marketplace add markaestro/markaestro-agents reads it. The skill alone can be copied to ~/.claude/skills/markaestro |
MCP Registry (com.markaestro/mcp) |
After the npm publish of the same version: mcp-publisher login http --domain markaestro.com --private-key <hex> then mcp-publisher publish from mcp/. The public key is served at /.well-known/mcp-registry-auth |
Glama (markaestro/markaestro-agents) |
Admin, Dockerfile: build step npm install -g @markaestro/mcp@<version>, CMD markaestro-mcp; Build, then Create Release |
Development
cd mcp
npm install
npm run build
MARKAESTRO_API_KEY=mk_test_... MARKAESTRO_BASE_URL=http://localhost:3000 npm run smoke # local stdio
MARKAESTRO_API_KEY=mk_test_... MARKAESTRO_BASE_URL=http://localhost:3000 npm run smoke -- --remote # hosted endpoint
Unit tests live in src/__tests__ and run with the repository's npm test.
The smoke script starts the built server over stdio, lists tools, reads the
brand, creates a draft, reads it back, and deletes it. Nothing is published.
Markaestro MCP Fragen
Wie füge ich Markaestro MCP zu Claude Code hinzu?
Führe claude mcp add --env 'MARKAESTRO_API_KEY=<YOUR_MARKAESTRO_API_KEY>' mcp -- npx -y @markaestro/mcp in deinem Terminal aus. Füge --scope user hinzu, damit der Server in jedem Projekt verfügbar ist.
Wie füge ich Markaestro MCP zu Cursor hinzu?
Öffne ~/.cursor/mcp.json und füge den Server unter mcpServers hinzu, mit der Cursor-Config aus dem Installationsabschnitt oben.
Welche Tools bietet Markaestro MCP?
Er stellt 18 Tools bereit, darunter list_products, list_destinations, get_brand_profile, create_post, update_post.
Kann der KI-Agent veröffentlichte Posts löschen?
Nein, der Agent kann keine veröffentlichten Posts löschen, sie von einer Plattform entfernen oder eine Evergreen-Queue archivieren; diese Aktionen müssen vom User durchgeführt werden.
Wie geht der Server mit doppelten Posting-Anfragen um?
Der Server sendet bei jeder Mutation einen Idempotency-Key, sodass wiederholte Anfragen die ursprüngliche Aktion ausführen, anstatt einen doppelten Post zu erstellen.
Gibt es eine Möglichkeit, den Server im Read-only-Modus zu nutzen?
Ja, du kannst den Header x-markaestro-read-only: 1 senden, um nur die Reading-Tools zu erhalten.
Unterstützt der Server lokale Datei-Uploads?
Ja, wenn du den Server lokal über stdio ausführst, kann das upload_media Tool Dateien direkt von deinem lokalen Rechner lesen.