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