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