Your agent can request the research. A human still hits post.
RepoMuse exposes the same research-and-draft pipeline the web studio uses as an MCP endpoint - 33 tools, OAuth or a Bearer token. Your agent can draft for free. It never publishes to a platform on its own.
How it works
POST https://repomuse.com/mcp
Authorization: Bearer rm_live_...
Content-Type: application/json
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "generate_social_posts",
"arguments": {
"projectId": "proj_...",
"authorId": "author_...",
"platform": "x",
"format": "THREAD",
"prompt": "Shipped multi-platform support today"
}
}
}| Protocol | JSON-RPC 2.0 over HTTP, standard MCP |
| Endpoint | POST /mcp |
| Auth | OAuth 2.1 (PKCE), or a Bearer token minted at /app/tokens |
| Tools | 33, including a free drafting packet, platform validation, and agent drafts |
| Billing | Free agent path spends nothing. Paid studio drafts share the same wallet. |
| Publishing | Never. Every tool returns a draft or record; nothing posts to a platform |
Not a raw Twitter-posting MCP server
Most social MCP servers wrap the platform's own API: they authenticate as your account and post directly. RepoMuse's endpoint sits one layer earlier - it reads your product profile, your author voice, and your linked repository, then returns a draft. What goes out under your name is still your call, made by a human, every time.
FAQ
Is this another "post to Twitter" MCP server?
No. Generic Twitter MCP servers wrap the platform API to post or manage an account. RepoMuse's MCP endpoint does the research and drafting step - it returns a finished draft your agent (or you) still has to post. It never touches your social account.
What can an agent actually do over MCP?
Fetch a drafting packet, write locally, validate against platform rules, and store a draft for free. Or request paid server-side generations. Same voice corpus and post revisions as the web studio, exposed as 33 typed tools.
How is a request authenticated?
Two ways. MCP clients that support OAuth connect in one click: /mcp returns a 401 pointing at the discovery documents, the client registers itself, and a human approves the read and generate scopes on a RepoMuse consent screen. Otherwise a signed-in human mints an rm_live_ Bearer token at /app/tokens. The free agent path spends nothing. Paid studio drafts share the same wallet. Access can be revoked at any time.
Is there a REST alternative to MCP?
Yes - the same operations are available as REST at /api/v1, documented with a full OpenAPI schema at /api/v1/openapi.json and a browsable reference at /docs/api.
Mint a token, point your agent at it.
The free MCP path spends nothing. $12/mo gets you 300 server-side drafts a month if you want us to write them.