Connect Codex, Claude Code, OpenCode and other clients

Codex: Connect uses the Codex command-line tool if available. If it is absent, the window prints the exact executable path for manual setup. In the app, choose Settings → MCP servers → Add server, use name battlemap, transport STDIO, and paste that path into Command. Leave arguments empty, save, and restart the connection. No separate runtime installation is needed. This manual route follows OpenAI’s instructions.

Claude Code: Connect uses the claude command-line tool. It does not set up the Claude desktop chat app; for that, use the .mcpb extension in Install from Claude. Do not combine a Connect registration with the plugin or extension: every tool would appear twice. Running Connect again at the same location is harmless. If an existing user entry points to an older companion, Connect stops, shows the command that entry runs, and says whether that file still exists. Remove that one entry before running Connect again:

claude mcp remove --scope user battlemap

Keep the previous companion until replacement setup succeeds. Setup does not silently remove a different registration. If the claude command is missing, finish installing Claude Code, reopen the Connect file, and try again.

Any AI client that can run a local (STDIO) MCP server works; Codex, Claude Code and OpenCode have a Connect file. In your client’s MCP settings, add a local STDIO server named battlemap, with the companion executable’s full path as the command and no arguments: battlemap-mcp.exe on Windows, battlemap-mcp on macOS and Linux, inside the folder you extracted. Your client starts it for you. See technical configuration.

OpenCode: open Connect OpenCode in the companion folder. It installs the map-making skills into ~/.config/opencode/skills/ and registers the companion with OpenCode 2’s opencode mcp add --global. That command replaces an entry of the same name without asking, so the Connect file first checks ~/.config/opencode/opencode.json and leaves a battlemap entry that runs another command alone. Restart OpenCode and check with opencode mcp list. Right after OpenCode’s background service starts, it can say no servers are configured; wait a few seconds and run it again.

With OpenCode 1, which has no mcp add, or without opencode on your PATH, the Connect file prints the entry instead and never edits your settings: paste it inside "mcp" yourself. It looks like this, with your companion’s full path:

{
  "mcp": {
    "battlemap": {
      "type": "local",
      "command": ["/full/path/to/battlemap-mcp"],
      "enabled": true
    }
  }
}

The map-making skills are in the companion folder under _internal/battlemap_mcp/skills_payload/, one folder per skill. To use them in a client without a Connect file, copy those folders to wherever the client loads skills from; for OpenCode, that is ~/.config/opencode/skills/.