Krevaya is the review-first content workspace Roo Code drives through our hosted MCP server. Drafts wait for your approval; auto-publish is opt-in. Last updated October 2026.
Mint a key, paste one snippet, and ask. Roo Code discovers the Krevaya tools your key allows and calls them for you; nothing publishes until you approve it.
Paste this with a key from Settings → API keys. Give the key only the scopes Roo Code needs.
{ "mcpServers": { "krevaya": {
"type": "streamable-http",
"url": "https://api.krevaya.com/mcp",
"headers": { "Authorization": "Bearer krv_..." },
"timeout": 600
} } }Open it from Roo Code's MCP Servers panel. The default timeout is 60 seconds, too short for a repurpose run.
Once connected, Roo Code calls the Krevaya tools. Approved and scheduled posts publish on time, even after you close it.
Check my Krevaya queue, approve the drafts that sound like me, and schedule them for the best times.
Done. Three drafts approved and scheduled: Tue 9:00 AM, Thu 6:10 PM, Sat 10:30 AM. One draft rejected as too salesy, with the reason noted. Nothing has published yet; the scheduled posts go out at those times.via Krevaya · get_queue_summary, approve_post, reject_post, get_best_times, schedule_post
Connect your accounts in Krevaya once. From then on Roo Code can draft for any of them, and Krevaya publishes at the time you set.
Write, review, design, schedule, and measure, all through the Krevaya tools it discovers once the server is added.
Tell Roo Code what to draft, approve, or schedule. It calls the Krevaya tools for you; no menus, no forms.
Drafts land in your review queue. Nothing publishes until you approve it, and auto-publish is opt-in per pipeline.
Instagram, TikTok, Pinterest, Facebook, Threads, LinkedIn, and Bluesky, from one connection.
Draft a week from what's trending, pick the best times from your own engagement history, and schedule.
Copy a video template into a design, change titles or footage one layer at a time, and preview pages as images.
Scoped keys: a read-only key can look but never publish. Tools are filtered per key, and you can revoke one in a click.
MCP (Model Context Protocol) is the open standard that lets AI assistants call real tools. Krevaya hosts a remote MCP server, so Roo Code gets your whole content pipeline as tools without a local process. Read more on the MCP page →
# Krevaya MCP server
URL: https://api.krevaya.com/mcp
Transport: Streamable HTTP
Auth: Authorization: Bearer krv_...
# Tools, filtered to your key's scopes
read & triage · create · design · schedule & publish
media · measure · engagement · brand memory
# Ready-made prompts
content_ops · weekly_review · repurpose_source · plan_weekAnything you would ask a teammate: name the channels, the time, and the tone, and Roo Code handles the rest.
Draft a launch post for Instagram and LinkedIn about our new Friday hours, in my voice, and put both in my review queue.
Plan next week from what's trending in my niche and schedule the approved posts at my best times.
Repurpose this article into a Threads thread and a LinkedIn post. Make the thread contrarian.
Who should I reply to this morning? Draft the replies in my voice and I'll approve them.
The details that trip people up with this client, from our own testing.
Both connect to the same server and see the same tools. The difference is where you work.
| Roo Code | Cline | |
|---|---|---|
| What it is | A fork of Cline with modes and profiles | An open-source agent for VS Code |
| Transport key | type: streamable-http, plus a 600 s timeout | type: streamableHttp |
| Best for | Longer runs such as repurpose | Approve-as-you-go sessions |
Same server, same tools, same review queue. ChatGPT is the one gap: its connectors need OAuth, which Krevaya does not offer yet.
Krevaya hosts a remote MCP server. Add it to Roo Code with the snippet on this page and Roo Code gets Krevaya's tools: list and triage drafts, create posts, draft a week, repurpose a link, design and edit video templates, schedule, and read results. Everything runs through the same review-first pipeline as the dashboard.
Mint a key in Settings → API keys, choose its scopes, then add the server to mcp_settings.json. There is nothing to install on Krevaya's side; the server is hosted.
MCP access is included on Krevaya's Plus plan ($29 per month) and up, with the same usage allowances as the rest of your account. Roo Code's own requirements are set by Roo Code, not by Krevaya.
Only what you have approved. Drafts wait in the review queue; approved and scheduled posts publish at their time whether or not Roo Code is open. Auto-publish is opt-in per pipeline, and you can turn it back off any time.
No. Roo Code talks to Krevaya with a scoped API key, and Krevaya publishes through each platform's official API with tokens encrypted at rest. A read-only key cannot publish at all. Revoke a key in one click and the connection is gone.
Any channel connected to your Krevaya workspace: Instagram, TikTok, Pinterest, Facebook Pages, Threads, LinkedIn, and Bluesky. Available formats depend on the channel and your connected account.
Three things: the key is sent as an Authorization: Bearer header, the URL is exactly https://api.krevaya.com/mcp, and the key's scopes cover what you are asking for, because tools are filtered per key. For Roo Code specifically: type is streamable-http, hyphenated, and required.
Krevaya's Free plan does not include MCP access; it starts with Plus. Access is currently by invitation, so join the waitlist and we will be in touch when it is your turn.
MCP access is included from the Plus plan up. Join the waitlist and we'll be in touch when it's your turn.
Join the waitlist