Client Integration Guide

Connect Nexus Prime to the tools that actually drive the work.

Use this page to install the autonomous MCP profile, write the compact client-native instruction surface, verify the bridge, and debug the common failure modes.

Docs Shortcuts
Knowledge Base Core concepts, runtime behaviors, and API reference. Architecture Diagrams Visual schematics for memory, swarms, tokens, and request flow. GitHub Repository Source, releases, issues, and automation workflows.

Automated Setup

The fastest path installs both MCP config and the right client-native Nexus Prime instructions.

# Globally install first
npm install -g nexus-prime

# Run setup for your tool
nexus-prime setup cursor
nexus-prime setup claude
nexus-prime setup opencode
nexus-prime setup windsurf
nexus-prime setup antigravity

Verification

  1. Open the AI or settings pane in your tool.
  2. Confirm `nexus-prime-mcp` appears in connected servers.
  3. Call nexus_session_bootstrap with a real task to verify the bridge and the default execution path.
  4. For non-trivial work, follow with nexus_orchestrate instead of manually chaining low-level tools.

Supported Tools

Cursor

Automated: nexus-prime setup cursor
MCP config: ~/.cursor/mcp.json
Project rule: .cursor/rules/nexus-prime.mdc

Claude Code

Automated: nexus-prime setup claude
MCP config: ~/.claude-code/mcp.json
Project instruction: .agent/client-bootstrap/claude-code.md

Opencode

Automated: nexus-prime setup opencode
MCP config: ~/.opencode/config.json
Project instruction: .agent/client-bootstrap/opencode.md

Windsurf

Automated: nexus-prime setup windsurf
MCP config: ~/.windsurf/mcp.json
Project rule: .windsurfrules

Antigravity / OpenClaw

Automated: nexus-prime setup antigravity
MCP config: ~/.antigravity/mcp.json
Home-scoped skill bundle: ~/.antigravity/skills/nexus-prime/

Codex

Codex uses the repo-local AGENTS.md plus the autonomous MCP profile. There is no separate Codex-only setup artifact today.

Troubleshooting

Polluted stdout

Use npx -y nexus-prime mcp or the published CLI. Extra stdout breaks JSON-RPC framing in strict MCP clients.

Wrong MCP profile

External clients should use NEXUS_MCP_TOOL_PROFILE=autonomous. The setup command writes this automatically so clients see nexus_session_bootstrap and nexus_orchestrate first instead of a noisy expert catalog.

Version mismatch

Ensure the client is picking up the latest npm version. Recent runtime behavior and dashboard fixes require the current `3.x` line.

Bridge verification

If the server appears connected but tools fail, run the MCP process directly and watch stderr for handshake and guardrail logs.