gauntlet_status — The Forge Gauntlet MCP Tool
gauntlet_status
(gauntlet status) is one of 3 tools on the
The Forge Gauntlet
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call gauntlet_status from your client
- Claude Code The Forge Gauntlet gauntlet_status run in your project directory
- Claude Desktop The Forge Gauntlet gauntlet_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor The Forge Gauntlet gauntlet_status ~/.cursor/mcp.json
- VS Code The Forge Gauntlet gauntlet_status .vscode/mcp.json
- Zed The Forge Gauntlet gauntlet_status ~/.config/zed/settings.json
- Windsurf The Forge Gauntlet gauntlet_status ~/.codeium/windsurf/mcp_config.json
- Cline The Forge Gauntlet gauntlet_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI The Forge Gauntlet gauntlet_status ~/.gemini/settings.json
- Grok The Forge Gauntlet gauntlet_status .mcp.json (in your project root)
- ChatGPT The Forge Gauntlet gauntlet_status Settings → Connectors → Advanced → Developer mode
- Claude.ai The Forge Gauntlet gauntlet_status Settings → Connectors → Add custom connector
- LangChain The Forge Gauntlet gauntlet_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http forge-gauntlet https://theagentforge.io/mcp/gauntletOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 6 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.