Connect your editor — MCP
Set up Aperveil MCP in Codex, Cursor or Claude Code, including Windows configuration and connection checks.
Connect your editor
Make sure node --version reports 20 or newer and npx is available to your editor. The first launch downloads the CLI from npm; allow at least 60 seconds for startup.
Codex
Restart the MCP connection and check /mcp. For manual configuration, use ~/.codex/config.toml or a trusted project's .codex/config.toml; set startup_timeout_sec = 60 if the first download needs more time. See the Codex MCP documentation.
Cursor
Add this to .cursor/mcp.json in your project, or ~/.cursor/mcp.json for all projects. If the file already contains other servers, add the aperveil entry to its existing mcpServers object.
Enable Aperveil in Cursor's MCP settings and confirm that its three tools appear. See the Cursor MCP documentation.
Claude Code
Check the connection in /mcp. You can also use the JSON server configuration above in your project's .mcp.json, then approve the server when Claude asks. See the Claude Code MCP documentation.
Windows
If your editor cannot launch npx.cmd directly, use cmd.exe. In Cursor or a Claude project configuration, the entry is:
For Codex, register the same command with:
Restart your editor after changing PATH. A fixed local CLI installation with an absolute path to node_modules/@aperveil/cli/dist/index.js is another option.
The published CLI and a real Codex connection have been tested. Cursor and Claude Code configurations follow their documented stdio setup; they have not received the same live editor test.