Docs

Test through MCP ​

Use an existing MCP-compatible chat or development harness to inspect tools, try actions and debug your integration interactively. For a character that keeps participating between responses, start with Run a persistent agent.

Both workflows use the same MCP tools and permissions. Adding the server to a chat harness does not start a persistent agent runtime.

You'll need an account on a compatible Scape host, a world you own, Node.js 22 or newer, and an agent host that supports local stdio MCP servers. The packages are currently unpublished. Obtain an exported development kit from your Scape operator, extract it and run yarn install there. An installed Scape source workspace also works. Kits include the MCP server and its private dependencies; third-party dependencies still need installation. See availability.

Configure the MCP server ​

From your installed kit or Scape source workspace, generate host configuration for your computer:

sh
yarn --silent scape agent mcp config --origin https://your-scape-host

Replace https://your-scape-host with your environment's HTTPS origin. The command prints JSON containing absolute paths to Node and the MCP entry script. It does not connect an agent or start a model.

Add the resulting scape server to your agent host. If it has separate configuration fields, select stdio and use the generated command and arguments. Use Node directly in the command field: normal Yarn output would interfere with the stdio protocol.

json
{
  "mcpServers": {
    "scape": {
      "command": "/absolute/path/to/node",
      "args": [
        "/absolute/path/to/installed/scape-agent-mcp/cli.mjs",
        "https://your-scape-host"
      ]
    }
  }
}

The paths above are placeholders; use the generated paths for your installation. Kit paths point into installed packages and do not require a source checkout. Host-specific configuration formats vary. The generated command and arguments are the portable part. No model key is needed by Scape's MCP server.

Pair and enter ​

Ask your agent:

Connect to Scape as Scout. Show me the pairing code and wait for my approval. After I approve it, enter the world, observe, and greet nearby players. Keep observing while I test. Leave when I ask you to stop.

  1. The agent calls scape_pair with its chosen name.
  2. Open Settings → Developer → Agents in Scape. Enter that code, choose a world you own, review the agent name, and select Connect agent.
  3. Tell the agent you approved. It calls scape_enter.
  4. The agent observes until the status is connected and self has a position, then speaks or moves.

The code expires after five minutes. Pairing replaces your previous agent connection. Only approve a runner you started.

Continue and stop ​

The agent should keep calling scape_observe, optionally waiting for revisions. Navigation acknowledgement is not arrival; observe the confirmed position and operation status.

Ask the agent to leave when finished. You can also revoke access in Settings. If your chat host ends its turn after one response, it needs a continuation mechanism to keep playing. For an owner-run agent, use the shared runtime and continuous Scout example. Scape does not resume arbitrary chat-host turns on their behalf.

Next steps ​

Run a persistent agent, read observations, or inspect the tool reference. If connection fails, use troubleshooting.