Start here
One setup flow for every editor
Install and log in to the shim once, then run the matching install command for your editor. The shim writes the correct MCP configuration and keeps the API key out of your editor configuration.
cargo install falsegreen
falsegreen login --token YOUR_FALSEGREEN_KEY
Replace YOUR_FALSEGREEN_KEY with your key, then reload or restart your editor.
01 · Codex
Connect Codex
Run the matching shim command from a terminal:
falsegreen install codex
The shim writes the editor’s MCP configuration for you. Reload Codex, then ask your agent to list its available MCP tools.
02 · GitHub Copilot
Connect GitHub Copilot
Run the matching shim command from a terminal:
falsegreen install github-copilot
The shim writes the editor’s MCP configuration for you. Reload GitHub Copilot, then ask your agent to list its available MCP tools.
03 · Claude Code
Connect Claude Code
Run the matching shim command from a terminal:
falsegreen install claude-code
The shim writes the editor’s MCP configuration for you. Reload Claude Code, then ask your agent to list its available MCP tools.
04 · OpenCode
Connect OpenCode
Run the matching shim command from a terminal:
falsegreen install opencode
The shim writes the editor’s MCP configuration for you. Reload OpenCode, then ask your agent to list its available MCP tools.
05 · Cursor
Connect Cursor
Run the matching shim command from a terminal:
falsegreen install cursor
The shim writes the editor’s MCP configuration for you. Reload Cursor, then ask your agent to list its available MCP tools.
06 · Finish
Verify the connection
Restart or reload your client, then ask it to list its available MCP tools. If authentication fails, run falsegreen status and check that your key is active.
Reference
CLI reference
falsegreen status shows authentication and device status. falsegreen logout deactivates the current device and frees an activation slot. falsegreen mcp runs the MCP server over STDIO.
Each license supports two activated devices. The service allows 60 requests per minute with a burst of 20; retry 429 responses after the Retry-After duration.