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