Arch MCP Tools

@koredev/arch-mcp-tools is a Model Context Protocol (MCP) server that connects your AI coding assistant to the Kore.ai Agent Platform. It gives the assistant a set of tools to build, evaluate, optimize, debug, and analyze agents on the platform — create and edit projects, agents, and tools; run evaluations; inspect live sessions and traces; and diagnose failures — directly from your editor or terminal.

It works with any MCP-compatible client (Claude Code, Cursor, VS Code, Codex CLI, and others). The server is exposed to clients under the name arch-agent-platform, and its tools are prefixed platform_* and debug_*.

Requirements

• Node.js 18 or newer — the server runs via npx, no separate install needed.
• A Kore.ai Agent Platform account — you authenticate on first connect (see Authentication).

Install

@koredev/arch-mcp-tools is a standard stdio MCP server. Every client launches it the same way:

command:  npx
args:     -y  @koredev/arch-mcp-tools

Add it under a server named arch-agent-platform using your client's config below. (No environment is baked in — see Choosing an environment.)

Claude Code

claude mcp add arch-agent-platform -- npx -y @koredev/arch-mcp-tools

Or add it to .mcp.json (project) or ~/.claude.json (global):

{
  "mcpServers": {
    "arch-agent-platform": {
      "command": "npx",
      "args": ["-y", "@koredev/arch-mcp-tools"]
    }
  }
}

Cursor

Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

{
  "mcpServers": {
    "arch-agent-platform": {
      "command": "npx",
      "args": ["-y", "@koredev/arch-mcp-tools"]
    }
  }
}

VS Code (GitHub Copilot)

Add to .vscode/mcp.json — note the top-level key is servers (not mcpServers):

{
  "servers": {
    "arch-agent-platform": {
      "command": "npx",
      "args": ["-y", "@koredev/arch-mcp-tools"]
    }
  }
}

Codex CLI

codex mcp add arch-agent-platform -- npx -y @koredev/arch-mcp-tools

Or add to ~/.codex/config.toml — note this is TOML, not JSON:

[mcp_servers.arch-agent-platform]
command = "npx"
args = ["-y", "@koredev/arch-mcp-tools"]

Any other MCP client

Configure a stdio server with command npx and args ["-y", "@koredev/arch-mcp-tools"]. Optionally set an AGENTS_URL environment variable to pin an environment.

Or just ask your assistant

Paste this into your coding tool's chat and it will wire the server up for you:

Add an MCP server named arch-agent-platform that runs npx -y @koredev/arch-mcp-tools, and put it in this project's MCP config. Config location by tool — Claude Code: .mcp.json (mcpServers) · Cursor: .cursor/mcp.json (mcpServers) · VS Code: .vscode/mcp.json (servers) · Codex: ~/.codex/config.toml ([mcp_servers.arch-agent-platform]). Optionally set AGENTS_URL to my environment.

Choosing an environment

No environment is hardcoded. On first use, the tools ask which environment to connect to — or you can pin one by setting AGENTS_URL in the server's env (or by passing serverUrl to platform_connect).

| Environment | URL | | ----------- | -------------------------------- | | Production | https://agents.kore.ai | | Dev | https://agents-dev.kore.ai | | Staging | https://agents-staging.kore.ai | | QA | https://agents-qa.kore.ai |

Example with a pinned environment (Claude Code / Cursor shape):

{
  "mcpServers": {
    "arch-agent-platform": {
      "command": "npx",
      "args": ["-y", "@koredev/arch-mcp-tools"],
      "env": {
        "AGENTS_URL": "https://agents.kore.ai"
      }
    }
  }
}

Tools

Arch Build

Create and change platform projects, agents, tools, configuration, versions, deployments, and imports.

| Tool | Description | | ------------------------ | -------------------------------------------------------- | | platform_projects | Manage projects (list, get, create, update, delete) | | platform_agents | Manage agents (list, get, save_dsl) | | platform_versions | Manage agent versions (list, create, get, promote, diff) | | platform_deployments | Manage deployments (list, create, get, retire, rollback) | | platform_tools | Manage tools (list, get, create, update, delete, test) | | platform_import_export | Import and export projects | | platform_config | Manage project and LLM configuration | | platform_workspaces | List, switch, and inspect active workspaces |

Arch Evaluate

Generate eval assets, run eval workflows, and read CI evidence.

| Tool | Description | | -------------------------- | ------------------------------------------------ | | platform_eval_personas | Manage and generate eval personas | | platform_eval_scenarios | Manage and generate eval scenarios | | platform_eval_evaluators | Manage eval evaluators and templates | | platform_eval_sets | Manage eval sets | | platform_eval_runs | Manage eval runs, preflight, cases, and heatmaps | | debug_harness_logs | Get CI execution logs |

Arch Optimize

Validate packages, inspect compiler-visible models, and drive repair loops.

| Tool | Description | | ----------------------------- | ----------------------------------------------------------------------- | | platform_validate_package | Validate a local package and optional import preview | | platform_package_model | Show compiler-visible agents, tools, constraints, refs, and diagnostics | | debug_lint_abl | Run ABL repair and design lint checks | | debug_why_transcript_failed | Correlate transcript symptoms with ABL file/line causes | | debug_diagnose_transcript | Alias for transcript failure diagnosis |

Arch Debug

Connect to live sessions, trace failures, and inspect execution state.

| Tool | Description | | ---------------------------- | -------------------------------------------------- | | platform_connect | Connect and authenticate to the platform | | debug_list_agents | List available agents by domain | | debug_load_agent | Load an agent and create a debug session | | debug_send_message | Send a message to an agent | | debug_get_current_state | Inspect agent context, gather progress, flow state | | debug_traces | Search trace events (type, text, agent, error) | | debug_get_span_tree | View hierarchical execution flow | | debug_explain_decision | Explain agent decisions with context | | debug_get_flow_graph | View state machine graph (JSON or Mermaid) | | debug_get_errors | Get errors, warnings, and escalations | | debug_list_active_sessions | List observable sessions | | debug_session | Subscribe/unsubscribe to session traces |

Arch Analyze

Explain documentation, diagnostics, and system health signals.

| Tool | Description | | ----------------------- | ------------------------------------------ | | debug_docs | Get or search ABL documentation | | debug_diagnose | Diagnose agent config and execution issues | | debug_analyze_session | Automated session diagnostics |

Authentication

Authentication is automatic when you call platform_connect — it tries, in order:

1. Explicit token — pass an authToken parameter.
2. Stored credentials — reads the same encrypted credential store used by kore-platform-cli login.
3. Device authorization — opens your browser and polls until approval completes in the same platform_connect call.

Credentials are saved for reuse in future sessions.

License

MIT — see LICENSE.