Krevaya is the review-first content workspace Kimi Code drives through our hosted MCP server. Drafts wait for your approval; auto-publish is opt-in. Last updated October 2026.
Add the server, sign in, and ask. Kimi Code discovers the Krevaya tools you approved and calls them for you; nothing publishes until you approve it.
Sign in when Kimi Code asks, or paste a key from Settings → API keys with the second tab.
{ "mcpServers": { "krevaya": {
"url": "https://api.krevaya.com/mcp",
"headers": { "Authorization": "Bearer krv_..." }
} } }~/.kimi-code/mcp.json for every project, or .kimi-code/mcp.json in one. /mcp-config in the TUI edits the same file, and Kimi Code Desktop and the VS Code extension share it.
Once connected, Kimi 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 Kimi 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 Kimi 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 connections: a read-only one can look but never publish. Tools are filtered per connection, 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 Kimi 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: OAuth sign-in, or 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 Kimi 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.
| Kimi Code | Codex | |
|---|---|---|
| What it is | Moonshot's coding agent, terminal and desktop | OpenAI's coding agent |
| How it connects | mcp.json with url and a header | codex mcp add with the key in an environment variable |
| Best for | K3 with a long context | The ChatGPT ecosystem |
Same server, same tools, same review queue. Sign in from the apps that ask for it; paste a key everywhere else.
Krevaya hosts a remote MCP server. Add it to Kimi Code with the snippet on this page and Kimi 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.
Add the server to mcp.json, with a key from Settings → API keys, or leave the key out and sign in when Kimi Code asks: Krevaya opens a page where you choose what it may do. There is nothing to install; 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. Kimi Code's own requirements are set by Moonshot AI, 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 Kimi Code is open. Auto-publish is opt-in per pipeline, and you can turn it back off any time.
No. Kimi Code talks to Krevaya with a scoped API key or a scoped token from the sign-in, and Krevaya publishes through each platform's official API with tokens encrypted at rest. A read-only connection cannot publish at all. Revoke it in one click under Settings → API keys 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 URL is exactly https://api.krevaya.com/mcp, the sign-in finished (the connection is listed under Settings → API keys), and the scopes you approved cover what you are asking for, because tools are filtered per connection. For Kimi Code specifically: A url with no transport is Streamable HTTP, which is right; set transport only for a legacy SSE server.
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