Skip to main content
Agent Platform exposes its features through a Model Context Protocol (MCP) server. Your AI assistant can connect to the platform and perform platform operations to let you build, evaluate, optimize, debug, and analyze agents. Use MCP server, to perform these tasks from within your IDE, command-line, or terminal, without context-switching. To use the MCP server, you install @koreai/arch-mcp-tools and configure your AI assistant.

Prerequisites

  • Node.js 18 or later — We recommend LTS version. The server starts using npx command.
  • Acess to Agent Platform account. When you connect for the first time, you must authenticate.
  • MCP-compatible client.

Install and configure

The server (@koreai/arch-mcp-tools) is a standard stdio MCP server. The clients launch it using the command: npx -y @koreai/arch-mcp-tools. In your client’s config, you add it as a server named: arch-agent-platform. The unpinned form follows the npm latest tag; use @koreai/arch-mcp-tools@1.5.0 for a reproducible install. By default, no environment is set. See Choose an environment to pin one. Provide the environment URL in one of the following ways:
  • In the configuration file, add as value of AGENTS_URL parameter in the env. For environment, see the list of region-specific platform URLs.
  • Pass serverUrl to platform_connect.
  • On the first use, the tool asks you for the environment.
Or add it to .mcp.json (project) or ~/.claude.json (global):
Or add to ~/.codex/config.toml. Note that this file is TOML, not JSON:
Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
Add to .vscode/mcp.json. Note that the top-level key is servers, not mcpServers:
Configure a stdio server with command npx and args ["-y", "@koreai/arch-mcp-tools"]. Optionally, set an AGENTS_URL variable to pin an environment. Alternatively, use a version of the following prompt in your AI coding tool’s chat for it to do the configuration.

Authenticate

Authentication is automatic when you call platform_connect — it tries the following methods in the 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 stored securely and reused in future sessions.