hn-hiring-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HN_HIRING_MCP_CACHE_DIR | No | Directory used for the on-disk response cache (default `~/.cache/hn-hiring-mcp`, or `off` to disable disk caching). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_hiring_threadsB | Lists the most recent monthly "Ask HN: Who is hiring?" threads, newest first. |
| search_jobsA | Searches one month of "Who is hiring?" posts. All filters are optional and combined with AND. Returns compact summaries; call get_job for the full text of a post. |
| get_jobA | Returns the full text and parsed fields of one job post by its HN id (from search_jobs). |
| hiring_trendsA | For each of the last N monthly threads, counts how many posts mention each technology and how many offer remote/hybrid/onsite. Good for questions like 'is demand for Rust growing?'. The first call for many months can take ~1 s per uncached month. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: listing threads, searching across posts, retrieving a single post, and aggregating trends. Their boundaries are explicit and the descriptions cross-reference each other (search returns summaries, get_job fetches full text), so misselection is unlikely.
Three tools follow a verb_noun pattern (list_hiring_threads, search_jobs, get_job), but hiring_trends breaks the pattern as a noun phrase. The deviation is minor and the intent remains clear.
Four tools map cleanly onto the read-only domain of listing, searching, retrieving, and analyzing HN hiring posts. Each tool earns its place without redundancy or padding.
The set covers discovery (list/search), retrieval (get_job), and analytics (hiring_trends), which is solid for a read-only surface. Minor gaps like company- or role-level aggregation are absent, but agents can work around these via search.