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 - 41 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": "make_quick_start_draft",
"arguments": {
"task": {
"purpose": "post",
"prompt": "I removed a setup step so people can start writing immediately."
},
"idempotencyKey": "unique-key-for-this-task"
}
}
}Quick-start costs 1 credit for two drafts (Improve: one draft). Poll the returned generation.id with get_generation. Reuse the same idempotency key for identical retries; get user approval before spending.
| 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 | 41, including quick-start tasks, a shared Drafts library, platform limits, and free local drafting |
| 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 |
Know the limits before writing
Call get_platform_limits, then validate_social_parts for exact validation.
Input safety bounds are not platform allowances. Limits apply to each part, not the whole thread.
| Platform | Per-part limit | Threads |
|---|---|---|
| X | 280 weighted characters | 2-25 parts |
| Threads | 500 graphemes | 2-25 parts |
| 3000 graphemes | Not supported | |
| Bluesky | 300 graphemes and 3000 UTF-8 bytes | 2-25 parts |
X URLs count as 23; CJK characters generally count as two. Other platforms count Unicode grapheme clusters, not JavaScript string.length. A single POST always has exactly one part.
Edits are free: fetch get_social_post and supply the latest expectedRevisionId. Errors return a safe code, message, field issues, and recovery hint. On revision conflict, fetch and review again; never overwrite blindly. Nothing posts automatically.
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?
Use Post, Reply, Quote, or Improve without project setup, search saved drafts, and edit their revisions. Or fetch a drafting packet, write locally, validate against platform rules, and store a draft for free. Paid server-side generation is optional. The same voice corpus and revisions as the web studio are exposed as 41 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.