Core concepts

MCP servers

RAYS connects to Model Context Protocol (MCP) servers so the default agent orchestrator can use external tools — browsers, GitHub, databases, 3D apps, anything that exposes an MCP server over stdio.

How it works

  1. RAYS spawns selected servers as child processes (command + args).
  2. RAYS speaks MCP over the process's stdin/stdout.
  3. At connect time, list_tools registers tools under server_name/tool_name.
  4. For each MCP step, a dynamic sub-agent loops until its objective is met.

Where to configure

  • config.yaml → mcp_servers: — install defaults.
  • ~/.rays/mcp.json — global, all projects (recommended).
  • <project>/.rays/mcp.json — project only (highest priority).

Example — Blender MCP

{
  "mcp_servers": [
    {
      "name": "blender",
      "description": "Blender 3D scene tools",
      "command": "uvx",
      "args": ["blender-mcp"],
      "env": {
        "BLENDER_HOST": "localhost",
        "BLENDER_PORT": "9876"
      }
    }
  ]
}

Run /mcp in RAYS to see configured servers and connection status.

RAYS vs Claude / Cursor

RAYS uses an mcp_servers array, not Claude'smcpServers object. The inner fields (command,args, env) are the same — just copy the server entry into the RAYS array.