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