Jobs data · https://boards-api.greenhouse.io/v1
set up treg — https://treg.to/llms.txt
claude mcp add --transport http treg https://treg.to/mcp
Settings → Connectors → add https://treg.to/mcp as a custom connector.
Add https://treg.to/mcp as a remote MCP connector in its tool settings.
Settings → Connectors → Add custom connector → https://treg.to/mcp.
Point it at https://treg.to/mcp (HTTP transport).
curl -fsSL https://treg.to/install.sh | sh
LangChain, CrewAI or any code: /call/<tool-id> + X-Treg-Token: <token>. No SDK.
Using treg, a company's open job postings. Show me the price first.
treg call greenhouse.companies.jobs --query board_token=discord
Its tools are free and need no key: there is nothing to connect.
No charge per call and no markup.
A free treg.to account is all it takes: no card, and no account with the provider.
Greenhouse Job Board is a public API: no account, no key.
Another provider is a different word in the prompt, not a new integration.
The same token calls Apollo.io, Ashby job boards, Hirebase and 3,647 other tools.
greenhouse.companies.jobsgreenhouse.companies.jobs.departmentsgreenhouse.companies.jobs.detailgreenhouse.companies.jobs.officesReliability badges come from live traffic through treg.to. Live-verified means a successful provider check; it does not verify every request variant.
No. Greenhouse Job Board is a public API with no key: there is nothing to connect.
Nothing. treg.to does not charge for these calls.
Run: claude mcp add --transport http treg https://treg.to/mcp. One MCP server carries Greenhouse Job Board and the rest of the catalog.
Anything that speaks MCP (Claude Code, Claude Desktop, ChatGPT, Codex, Cursor, Grok) and anything that can make an HTTP request (LangChain, CrewAI, LlamaIndex, plain code).
No. treg.to relays Greenhouse Job Board's real public API: the request is the provider's own, no credential is added, and the answer is relayed verbatim. The official Greenhouse Job Board channels are linked above.