Custom MCP Client Setup
Configure Forge as an MCP server for any MCP-compatible tool.Generic Configuration Pattern
All MCP clients follow a similar pattern. Forge uses standard MCP protocol.Standard Configuration
Advanced Mode
Common MCP Clients
Roo Code
Gemini CLI
Continue.dev
Configuration Elements
Required Fields
| Field | Value | Description |
|---|---|---|
command | "npx" | Package runner command |
args | ["automagik-forge", "--mcp"] | Forge with MCP mode |
PROJECT_ID | UUID | Your Forge project ID |
Optional Fields
| Field | Value | Description |
|---|---|---|
name | "automagik-forge" | Server name identifier |
type | "stdio" | Communication protocol |
description | Custom text | Server description |
Getting Your Project ID
1
Start Forge
2
Navigate to Project
Open browser, create or select your project
3
Copy UUID
From the browser URL:
Testing Your Configuration
After configuring, test with these commands:automagik-forge in the list.
Troubleshooting
Find your client's MCP config location
Find your client's MCP config location
Check your client’s documentation for:
- “MCP configuration”
- “External tools”
- “Model Context Protocol”
- “Extensions” or “Plugins”
- Settings UI → MCP Servers
- Preferences → Tools → MCP
- Config file:
~/.config/<client>/config.json
Verify Forge is accessible
Verify Forge is accessible
Test Forge command directly:Should start the MCP server without errors.
Check Project ID validity
Check Project ID validity
Ensure:
- Project exists in Forge UI
- UUID is exact (no extra spaces/quotes)
- Format is correct:
proj_xxxxxor full UUID
Enable debug logging
Enable debug logging
Some clients support debug mode:Check client logs for MCP connection errors.

