Connect An AI Agent
Connect An AI Agent
Section titled “Connect An AI Agent”SuperDev is useful once the agent can call its MCP tools. This is a one-time setup: keep the desktop app running, install the MCP entry for your coding agent, and reload the agent so it discovers the tools.
What Gets Installed
Section titled “What Gets Installed”SuperDev supports Claude Code, Codex, and Cursor.
| Agent | MCP config | Skill directory | Session hook |
|---|---|---|---|
| Claude Code | ~/.claude.json | ~/.claude/skills/superdev | ~/.claude/settings.json |
| Codex | ~/.codex/config.toml | ~/.codex/skills/superdev | ~/.codex/hooks.json |
| Cursor | ~/.cursor/mcp.json | ~/.cursor/skills/superdev | ~/.cursor/hooks.json |
The skill matters as much as the MCP entry. It tells the agent to use SuperDev for services, logs, browser control, approvals, and verification instead of starting processes or tailing files by hand.
Codex Trust Step
Section titled “Codex Trust Step”Codex requires one extra trust step for unmanaged command hooks. After installation, open the Codex CLI and review the hook with /hooks; otherwise the MCP entry may exist but the SessionStart hook will not be trusted.
Verify
Section titled “Verify”Ask the agent to list its SuperDev capabilities and run one read-only call such as get_runtime_snapshot or list_services. Only after a read succeeds should it attempt write operations.
Common Failures
Section titled “Common Failures”- Tools do not appear: reload the AI tool and confirm the MCP entry was written to the profile it actually uses.
- Calls time out: confirm the SuperDev desktop app is running and the local agent URL is reachable.
- Codex setup looks installed but rules do not fire: run
/hooksand trust the hook.