kura-mcp-agent-import

MCP server that exposes Kura's agent-import tools as first-class tool calls in Claude Desktop, Cursor, and Claude Code.

Install

No global install needed — npx invokes it on demand:

// ~/.claude/.mcp.json  (or Claude Desktop / Cursor MCP settings)
{
  "mcpServers": {
    "kura-agent-import": {
      "command": "npx",
      "args": ["-y", "kura-mcp-agent-import"],
      "env": {
        "KURA_API_KEY": "kura_<your-key>",
        "KURA_BASE_URL": "https://orchestrator-production-1d88.up.railway.app"
      }
    }
  }
}

Or install globally if you prefer:

npm install -g kura-mcp-agent-import
# then point the MCP config at the installed binary:
# "command": "kura-mcp-agent-import"

Generate KURA_API_KEY at www.kurawebsites.com/account/api-keys. The key must have scope agent-import (the default for customer-minted keys).

Tools

| Tool | Args | Returns | | --- | --- | --- | | kura_validate_submission | { directory } | Validation result with errors/warnings | | kura_submit_project | { directory } | { projectId, slug, repoUrl, hubUrl, buildStatus } | | kura_get_project_status | { projectId } | Current project state + live URL |

All three accept absolute or relative paths and resolve them against the MCP server's working directory (which is your client's cwd).

Protocol

Implements newline-delimited JSON-RPC 2.0 over stdio. No @modelcontextprotocol/sdk dep — the protocol surface is small (initialize, tools/list, tools/call, ping, notifications/*) so it's implemented directly in ~200 lines.

Contract

See www.kurawebsites.com/agent-docs for the kura.config.json schema and per-framework rules your agent must follow.

Source

This package lives in github.com/benbybee/kura-orchestrator/tree/main/mcp/agent-import.