get_native_depth — hypernatt-terminal MCP Tool Read-only
get_native_depth
(get native depth) is one of 4 tools on the
hypernatt-terminal
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_native_depth from your client
- Claude Code hypernatt-terminal get_native_depth run in your project directory
- Claude Desktop hypernatt-terminal get_native_depth ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor hypernatt-terminal get_native_depth ~/.cursor/mcp.json
- VS Code hypernatt-terminal get_native_depth .vscode/mcp.json
- Zed hypernatt-terminal get_native_depth ~/.config/zed/settings.json
- Windsurf hypernatt-terminal get_native_depth ~/.codeium/windsurf/mcp_config.json
- Cline hypernatt-terminal get_native_depth ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI hypernatt-terminal get_native_depth ~/.gemini/settings.json
- Grok hypernatt-terminal get_native_depth .mcp.json (in your project root)
- ChatGPT hypernatt-terminal get_native_depth Settings → Connectors → Advanced → Developer mode
- Claude.ai hypernatt-terminal get_native_depth Settings → Connectors → Add custom connector
- LangChain hypernatt-terminal get_native_depth pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http hypernatt-terminal https://hypernatt.com/mcp/protocolOther 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.