Skip to content

Supported AI Coding Agents

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.

AgentIDMCP ConfigHooks
Claude Codeclaude-code.mcp.json.claude/settings.json
Cursorcursor.cursor/rules/mcp.jsonCursor hooks config
GitHub Copilotcopilot.vscode/settings.jsonVS Code config
Gemini CLIgemini-cli~/.gemini-cli/mcp.jsonGemini CLI config
OpenCodeopencodeopencode.json
Codex CLIcodex-cli~/.codex-cli/mcp.json
Roo Coderoo-code.roo/mcp.json
Clinecline.cline/mcp.json

archcore init detects agents by looking for their configuration directories:

AgentDetected by
Claude Code.claude/ directory
Cursor.cursor/ directory
Copilot.vscode/extensions/ with GitHub Copilot
Gemini CLI.codex/ directory
OpenCodeopencode.json file
Codex CLI.codex-cli/ directory
Roo Code.roo/ directory
Cline.cline/ directory

If no agents are detected, Archcore falls back to configuring Claude Code.

Most agents use the standard mcpServers format:

{
"mcpServers": {
"archcore": {
"command": "archcore",
"args": ["mcp"]
}
}
}

GitHub Copilot uses VS Code’s server format:

{
"servers": {
"archcore": {
"type": "stdio",
"command": "archcore",
"args": ["mcp"]
}
}
}

Install MCP for a specific agent:

Terminal window
archcore mcp install --agent cursor

Install hooks for a specific agent:

Terminal window
archcore hooks install --agent claude-code

Hooks run automatically when an agent starts a session. Currently supported for Claude Code, Cursor, Gemini CLI, and Copilot.

The hook triggers archcore hooks <agent-id> session-start, which provides the agent with initial context about the .archcore/ directory.

See Hooks for details.