Skip to Content
IntegrationsOther Agents

Other Agents

Connect SpecForge to Gemini CLI, Codex CLI, OpenCode, and any MCP-compatible agent.

SpecForge works with any tool that supports MCP servers. Beyond Claude Code and Cursor, the CLI auto-detects and generates configuration for Gemini CLI, Codex CLI, and OpenCode. If your tool speaks MCP, SpecForge connects to it.

The Universal Pattern

Every integration follows the same three steps:

  1. MCP config — Point the tool’s MCP configuration to npx @specforge/cli@latest
  2. API key — Set SPECFORGE_API_KEY in the tool’s environment
  3. Agent instructions — A markdown file that tells the agent how to interact with SpecForge

specforge init handles all three for every detected tool. The details below are for manual setup or troubleshooting.

Gemini CLI

Automatic

specforge init

Generates .gemini/settings.json and GEMINI.md.

Manual

Create .gemini/settings.json at your project root:

{
  "mcpServers": {
    "specforge": {
      "command": "npx",
      "args": ["@specforge/cli@latest"]
    }
  }
}

⚠️ Gemini CLI reads the API key from your environment. Set SPECFORGE_API_KEY in your shell profile or .env file before starting Gemini CLI.

GEMINI.md is the agent instruction file — it tells Gemini how to work with SpecForge tools, which tickets to pick up, and how to structure its work.

Codex CLI

Automatic

specforge init

Generates .codex/config.toml and AGENTS.md.

Manual

Create .codex/config.toml at your project root:

[mcp_servers.specforge]
command = "npx"
args = ["@specforge/cli@latest"]
 
[mcp_servers.specforge.env]
SPECFORGE_API_KEY = "sf_live_..."

AGENTS.md is placed at the repository root. Codex CLI reads it automatically.

OpenCode

Automatic

specforge init

Generates opencode.json and AGENTS.md.

Manual

Create opencode.json at your project root:

{
  "mcp": {
    "specforge": {
      "type": "local",
      "command": "npx",
      "args": ["@specforge/cli@latest"],
      "env": {
        "SPECFORGE_API_KEY": "sf_live_..."
      }
    }
  }
}

OpenCode reads AGENTS.md from the repository root.

Detect All Tools at Once

If you have multiple tools installed, specforge scaffold detects all of them and generates everything:

specforge scaffold

This creates config files for every detected tool — .mcp.json for Claude Code and Cursor, .gemini/settings.json for Gemini CLI, .codex/config.toml for Codex CLI, and opencode.json for OpenCode.

Preview without writing:

specforge scaffold --dry-run

Agent Instruction Files

FileUsed byPurpose
CLAUDE.mdClaude CodeProject context anchor + SpecForge workflow instructions
GEMINI.mdGemini CLISpecForge workflow instructions for Gemini
AGENTS.mdCodex CLI, OpenCode, othersUniversal fallback — any tool that doesn’t have a dedicated instruction format reads this

✅ AGENTS.md is the universal instruction file. Tools without their own dedicated format (like CLAUDE.md or GEMINI.md) fall back to reading AGENTS.md at the repository root.

Any MCP-Compatible Agent

If your tool supports MCP but isn’t listed here, the pattern is the same:

  1. Point the MCP server config to npx @specforge/cli@latest
  2. Set SPECFORGE_API_KEY in the environment
  3. Place an instruction file at the repository root

The SpecForge MCP server exposes 22 tools via the standard MCP protocol. Any compliant client can discover and call them.

Next Steps

Cursor & VS CodeQuality Standards