The stdio MCP proxy (@aveiro/mcp-server) now accepts platform_comment_overrides on social drafts — matching the hosted MCP server and REST API. MCP platform keys are instagram, threads, and linkedin.
What we fixed
Per-platform first comments — the link-in-comments pattern — were already supported on POST and PATCH /api/v1/social/posts and on the hosted Aveiro MCP server. Agents using the stdio proxy (mcp/aveiro, published as @aveiro/mcp-server) could set a single first_comment but not platform_comment_overrides, so every platform shared one comment string.We aligned the proxy with the hosted tool registration:
platform_comment_overrides on aveiro_social_create_draft and aveiro_social_update_draft
Platform keys limited to instagram, threads, and linkedin — the platforms you can actually connect. X was removed from MCP enums because it cannot publish; legacy REST rows that reference x still work.
First comments are reviewed like captions and publish with the post after approval. See First comments publish with the post for the dispatch behavior and failure handling.
Who benefits
Cursor / Claude Desktop users on the stdio MCP server drafting multi-platform posts
Agents that put URLs in first comments and need shorter Threads copy vs longer LinkedIn context
Teams standardizing on one MCP surface without hosted vs proxy drift
Reconnect or restart the stdio server if your session cached the old tool schema.
