get-location — Levels.fyi MCP Tool Read-only
get-location
(get location) is one of 30 tools on the
Levels.fyi
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get-location from your client
- Claude Code Levels.fyi get-location run in your project directory
- Claude Desktop Levels.fyi get-location ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Levels.fyi get-location ~/.cursor/mcp.json
- VS Code Levels.fyi get-location .vscode/mcp.json
- Zed Levels.fyi get-location ~/.config/zed/settings.json
- Windsurf Levels.fyi get-location ~/.codeium/windsurf/mcp_config.json
- Cline Levels.fyi get-location ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Levels.fyi get-location ~/.gemini/settings.json
- Grok Levels.fyi get-location .mcp.json (in your project root)
- ChatGPT Levels.fyi get-location Settings → Connectors → Advanced → Developer mode
- Claude.ai Levels.fyi get-location Settings → Connectors → Add custom connector
- LangChain Levels.fyi get-location pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http levels-fyi https://mcp.levels.fyi/
Other tools on this server
- get-permissions
- get-salary-percentiles
- get-salaries-by-company-level
- search-raw-data-points
- get-company
- get-company-levels
- get-company-group
- search-companies
- search-companies-by-vesting
- search-top-companies
- get-location-stats
- search-locations
- get-job-family
- search-job-families
- search-job-titles
- search-focus-areas
- search-role-terms
- get-profile
- upload-resume
- add-salary-submission
- get-salary-submission-by-id
- get-vesting-schedules
- search-jobs
- get-job
- send-feedback
- search-all
- get-available-filters
- get-metric-explanation
- get-domain-knowledge
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.