mcp-add

MCP Add

Install a dotforge MCP server template into the current project's or global Claude Code configuration.

Input parsing

From $ARGUMENTS (format: mcp add <server> [--global]):

• Extract <server>: the word after mcp add — one of github, postgres, supabase, redis, slack
• Detect --global flag: if present, target ~/.claude/settings.json; otherwise target .claude/settings.json

Step 0: Validate

1. Verify the server template exists: $DOTFORGE_DIR/mcp/<server>/

   • If directory not found:

     ✗ Unknown server '{{server}}'.
     Available: github, postgres, supabase, redis, slack
     Usage: /forge mcp add <server> [--global]
     

     Stop.

2. Determine target settings path:

   • --global → ~/.claude/settings.json
   • default → .claude/settings.json
   • If target doesn't exist and not --global: warn "No settings.json found. Run /forge bootstrap first, or use --global to install globally." Stop.
   • If target doesn't exist and --global: create ~/.claude/settings.json with {"permissions": {"allow": [], "deny": []}, "mcpServers": {}}.

Step 1: Load template files

Read all three template files:

• $DOTFORGE_DIR/mcp/<server>/config.json
• $DOTFORGE_DIR/mcp/<server>/permissions.json
• $DOTFORGE_DIR/mcp/<server>/rules.md

From config.json:

• Server key: the non-metadata top-level key (e.g., "github", "postgres")
• Server config block: the value of that key (the object with type, command, args, env)
• Install note: the _install string — contains required env vars and instructions
• Ignore all keys starting with _ (metadata)

From permissions.json:

• allow: the allow array value (or [] if absent)
• deny: the deny array value (or [] if absent)
• Ignore all keys starting with _

Step 2: Check for existing configuration

Read the target settings.json.

Check if the server is already configured:

• Present if mcpServers.<server> key exists in settings, OR
• Present if any of the server's allow entries appear in permissions.allow