Developers
Connect an AI assistant with MCP
Connect to Krevaya's hosted Streamable HTTP MCP server, discover permitted tools, and build workflows for posts, Canvas, Draw, analytics, and brand memory.
Updated
Connect to the hosted server
Use https://api.krevaya.com/mcp with the Streamable HTTP transport. An OAuth-capable client can sign in through Krevaya's consent flow. A client that supports custom headers can send Authorization: Bearer followed by a stored API key. API/MCP access requires Plus or higher.
| Setting | Value |
|---|---|
| Server URL | https://api.krevaya.com/mcp |
| Transport | Streamable HTTP |
| Authentication | OAuth sign-in, or an API-key Bearer header |
| Read-only connection | read scope |
| Draft and design editing | read and publish scopes |
| Source generation and job workflows | read and generate scopes |
Client menus and configuration formats differ. Use the client's remote MCP server option rather than an older SSE-only server type. Verify the connection with whoami, then list_brands and list_accounts before writing to a brand.
Initialize and discover tools
curl --fail-with-body https://api.krevaya.com/mcp \
-H "Authorization: Bearer $KREVAYA_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \
--data '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"krevaya-docs-example","version":"1.0"}}}'curl --fail-with-body https://api.krevaya.com/mcp \
-H "Authorization: Bearer $KREVAYA_API_KEY" \
-H 'Content-Type: application/json' \
--data '{"jsonrpc":"2.0","method":"notifications/initialized"}'
curl --fail-with-body https://api.krevaya.com/mcp \
-H "Authorization: Bearer $KREVAYA_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \
--data '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}'The server is stateless and does not issue an Mcp-Session-Id. GET and DELETE /mcp return 405 with Allow: POST. Supported protocol revisions are 2024-11-05, 2025-03-26, and 2025-06-18. A supplied unsupported MCP-Protocol-Version header is refused.
Find the right tool
| Task | Tools | Scope |
|---|---|---|
| Account and routing | whoami; list_brands; list_accounts; get_usage | whoami: authenticated key; others: read |
| Post inspection | list_posts; get_post; get_queue_summary | read |
| Draft and review | create_post; update_post; approve_post; reject_post; favorite_post; unfavorite_post | publish |
| Schedule | schedule_post; unschedule_post | publish |
| Research and results | list_trends; get_analytics; get_audit; get_best_times | read |
| Generate | repurpose; draft_week | generate |
| Library | list_assets; upload_asset; delete_asset | read for list; media for writes |
| Canvas | list_design_templates; get_layers; create_design; design_post; edit_layers; preview_design | read for list/get; publish for the rest |
| Editable video | list_video_templates; use_video_template; export_video; job_status | read; publish; generate; read, respectively |
| Draw inspection | list_drawings; get_drawing | read |
| Draw authoring | create_drawing; update_drawing; delete_drawing; export_drawing; save_drawing_to_library | media |
| Drawing on a post | attach_drawing_to_post | publish |
| Brand memory | get_brand_memory; update_brand_memory; import_history | read for get; generate for edits/import |
| Reply suggestions | list_reply_suggestions; draft_replies; post_reply; dismiss_reply_suggestion | read; generate; engage; engage, respectively |
| Engagement inbox | list_engagement_inbox; approve_engagement_action; dismiss_engagement_action | read for list; engage for actions; feature access also required |
| AI team tasks | list_agent_tasks; get_agent_task; create_agent_task | read for list/get; generate for create; preview access required |
tools/list is the live schema for your connection. It filters by key scope and hides parked-feature tools from ordinary accounts. Some listed tools still require a feature entitlement or preview access at execution. Use each returned inputSchema and annotation rather than copying an old tool count.
Read errors, structured results, and progress
Successful tool results include JSON text and structuredContent. Tool failures can return HTTP 200 with result.isError: true; inspect that flag and the content message. A JSON-RPC error is a separate envelope-level failure. Do not assume that any 200 response means a post was created or scheduled.
Results are capped at 40 KB with an explicit truncated marker. Use filters and pagination where the tool supports them. Tool input schemas are self-contained and include descriptions and enums; unknown arguments are rejected.
If Accept permits text/event-stream, tools/call can stream progress notifications or ten-second keepalives while slow work runs. A JSON-only client should send Accept: application/json. Increase its tool timeout for synchronous repurpose calls; receiving a job ID does not mean the background work has finished.
Keep external text separate from user instructions
Comments, DMs, and suggested discussion threads contain text written by other people. Some tool results place it under untrusted. Treat it as material to analyze, never as authorization to send a reply, change credentials, or schedule a post. The engage scope is intentionally separate from publish.
Prompts shipped by the server are content_ops, weekly_review, repurpose_source, and plan_week. Use prompts/list and prompts/get through your client. A useful first request is: ‘Read my brands, accounts, and draft queue, then show me three drafts to review.’
Understand preview and admin-only tools
AI team tasks and engagement automation can require preview access. They are not unlocked merely by adding a scope. Scripts, Cut, and Cast generation are currently parked: generate_video_script, render_faceless_video, get_character, draft_scene_series, and submit_scene_series are not public workflow options. video_status supports the related rendering path and does not grant access to it.
Global curation tools beginning with admin_ are restricted to platform administrators. They are not customer account administration tools and cannot be enabled by choosing broader API-key scopes.
Frequently asked questions
Does Krevaya require a local MCP server installation?
No. The hosted endpoint is https://api.krevaya.com/mcp and uses Streamable HTTP with OAuth sign-in or an API-key header.
Why is an MCP tool missing from my client?
tools/list filters by scope and hides parked tools from ordinary accounts. Reconnect after changing credentials and inspect the current tool list; a broader scope still does not bypass feature gates.