Claude, Cursor, and Codex clients

Setup is not available yet

Opcodex MCP/agent mode is planned. The server package and compatibility matrix do not exist as verified release inputs for this guide. Every command, argument, transport setting, and tool name remains VERIFY; this page deliberately provides no executable setup snippet.

Client checklist

Client	What to verify when the server ships
Claude	Exact product (desktop or developer tooling), supported transport, config mechanism, permission prompts, model-provider handling of tool results
Cursor	Supported client version, project/user config scope, transport support, approval behavior, provider handling
Codex	Supported app or CLI version, MCP registration mechanism, allowed tools, approval behavior, model-provider handling

Configuration formats change. Use each client’s official documentation for the exact version you run; do not copy a guessed JSON key or an unrelated server command.

Connection procedure to validate

1. Obtain the server from the authenticated Opcodex release destination.
2. Confirm its Community compatibility and documented transport.
3. Start with a disposable project and the narrowest read-only access available.
4. Register the exact released command or endpoint using the client’s documented mechanism.
5. Inspect the advertised tool list and permissions before invocation.
6. Check what a tool result contains before allowing the client to send it to a model provider.
7. Verify disconnection, process shutdown, and logs.

No client configuration should contain committed API keys or tokens. A cloud-enabled assistant can receive analysis data even if the server runs on your machine. Explicit opt-in must account for that transfer.

Continue with MCP server scope or Community vs Pro.