Kora MCP
========

Kora (the Actava platform) exposed as a Model Context Protocol server, so a
coding agent can list, run and inspect agents without a browser.

Endpoints (streamable HTTP, stateless, JSON responses):

  https://kora-mcp.actava.ai/prod      production   api.actava.ai
  https://kora-mcp.actava.ai/stg       staging      api.stg.actava.ai
  https://kora-mcp.actava.ai/dev       development  api.dev.actava.ai

Auth: send your own Kora API key on every request. Nothing is stored here.

  Authorization: Bearer <KORA_API_KEY>      or      X-API-Key: <KORA_API_KEY>
  X-Organization-Id: <org id>               optional, system-scoped keys only

Claude Code:

  claude mcp add --transport http kora https://kora-mcp.actava.ai/stg \
    --header "Authorization: Bearer $KORA_API_KEY"

Cursor (.cursor/mcp.json):

  { "mcpServers": { "kora": { "url": "https://kora-mcp.actava.ai/stg",
      "headers": { "Authorization": "Bearer <KORA_API_KEY>" } } } }

Machine-readable: https://kora-mcp.actava.ai/openapi.json  ·  https://kora-mcp.actava.ai/llms.txt

Tools: list_agents, get_agent, run_agent, get_session, wait_for_session,
continue_session, resume_session, list_session_files, read_session_file,
export_session, org_agents_activity, org_usage, org_quota, org_roi,
list_organizations, list_api_runs, get_api_run.

Pipeline Builder tools, generated from the OpenAPI description: list_pipelines,
create_pipeline, get_pipeline, update_pipeline, delete_pipeline,
replace_pipeline_steps, list_pipeline_runs, run_pipeline, get_pipeline_run,
get_pipeline_run_steps, list_pipeline_templates, copy_pipeline_template.
(/v1/pipelines is the Pipeline Builder, NOT the "Agent Workspace" orchestration
feature — that is /v1/workspaces.)

Resources: kora://docs/quickstart, kora://docs/gotchas, kora://docs/agent-card,
kora://docs/openapi.json.

Source and issues: github.com/actava-ai/actava-vercel-apps/tree/main/apps/kora-mcp