Agent Integrations
Archcore supports 8 coding agents out of the box. Each agent gets MCP server configuration and (where supported) session hooks installed automatically during archcore init.
Support matrix
Section titled “Support matrix”| Agent | MCP | Hooks |
|---|---|---|
| Claude Code | Yes | Yes |
| Cursor | Yes | Yes |
| GitHub Copilot | Yes | Yes |
| Gemini CLI | Yes | Yes |
| OpenCode | Yes | — |
| Codex CLI | Yes | — |
| Roo Code | Yes | — |
| Cline | Manual | — |
MCP = agent can list, read, create, update documents through Archcore tools. Hooks = agent receives document context automatically at session start.
Auto-detection
Section titled “Auto-detection”archcore init detects agents by looking for their configuration directories:
| Agent | Detected by |
|---|---|
| Claude Code | .claude/ directory |
| Cursor | .cursor/ directory |
| GitHub Copilot | .github/copilot-instructions.md file |
| Gemini CLI | .gemini/ directory |
| OpenCode | opencode.json file or .opencode/ directory |
| Codex CLI | .codex/ directory |
| Roo Code | .roo/ directory |
| Cline | .clinerules/ directory |
If no agents are detected, Archcore falls back to configuring Claude Code.
MCP config locations
Section titled “MCP config locations”| Agent | ID | Config File |
|---|---|---|
| Claude Code | claude-code | .mcp.json |
| Cursor | cursor | .cursor/mcp.json |
| GitHub Copilot | copilot | .vscode/mcp.json |
| Gemini CLI | gemini-cli | .gemini/settings.json |
| OpenCode | opencode | opencode.json |
| Codex CLI | codex-cli | .codex/config.toml |
| Roo Code | roo-code | .roo/mcp.json |
| Cline | cline | VS Code globalStorage (manual) |
Manual installation
Section titled “Manual installation”Install MCP for a specific agent:
archcore mcp install --agent cursorInstall hooks for a specific agent:
archcore hooks install --agent claude-codeBest experience
Section titled “Best experience”For the best experience, use an agent that supports both MCP and hooks. Claude Code, Cursor, GitHub Copilot, and Gemini CLI currently offer the most complete integration — agents receive context at session start and have full document management tools available.
Agents without hook support (OpenCode, Codex CLI, Roo Code, Cline) still work well through MCP tools. The main difference is that you’ll need to explicitly ask the agent to check for documents rather than having context injected automatically.
Plugin vs CLI integration
Section titled “Plugin vs CLI integration”This page lists the CLI-level integrations — every supported agent gets MCP and (where possible) hooks.
Two of these hosts (Claude Code and Cursor) additionally support the higher-level Archcore Plugin — skills, tracks, built-in agents, and guardrails. See Plugin supported hosts for the plugin-specific matrix.
Next steps
Section titled “Next steps”- MCP server — how agents connect.
- Hooks — what the session-start hook emits.
- Commands — the
archcorecommands that drive integration.