validate_config_files — Nightbreak Forge MCP Tool
validate_config_files
(validate config files) is one of 10 tools on the
Nightbreak Forge
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call validate_config_files from your client
- Claude Code Nightbreak Forge validate_config_files run in your project directory
- Claude Desktop Nightbreak Forge validate_config_files ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Nightbreak Forge validate_config_files ~/.cursor/mcp.json
- VS Code Nightbreak Forge validate_config_files .vscode/mcp.json
- Zed Nightbreak Forge validate_config_files ~/.config/zed/settings.json
- Windsurf Nightbreak Forge validate_config_files ~/.codeium/windsurf/mcp_config.json
- Cline Nightbreak Forge validate_config_files ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Nightbreak Forge validate_config_files ~/.gemini/settings.json
- Grok Nightbreak Forge validate_config_files .mcp.json (in your project root)
- ChatGPT Nightbreak Forge validate_config_files Settings → Connectors → Advanced → Developer mode
- Claude.ai Nightbreak Forge validate_config_files Settings → Connectors → Add custom connector
- LangChain Nightbreak Forge validate_config_files pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http forge https://forge.nightbreak.io/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 11 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.