unofficial-HackerNews-MCP-CLI
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_storiesA | Get a list of HackerNews stories from a category, with full details. 'top', 'new' and 'best' draw from up to 500 stories; 'ask', 'show' and 'job' from up to 200. Each result includes title, url, score, author, comment count and the canonical HN discussion link. |
| get_itemA | Get a single HackerNews item (story, comment, job, poll, or poll option). Returns null if no item exists with that id. |
| get_itemsA | Get many items in one call, preserving order and dropping missing ids. |
| get_commentsA | Get the threaded comment tree for an item. Each comment includes a nested |
| get_userA | Get a HackerNews user's public profile (karma, about, created, submissions). Returns null if the user has no public activity or does not exist. |
| get_max_item_idA | Get the id of the most recently created item, useful for walking all items. |
| get_updatesA | Get the items and user profiles that changed most recently. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| daily_digest | Write a prompt that asks the agent to summarize the day's stories. `category` is the token the agent should pass to `get_stories` (top, new, best, ask, show, or job). It stays a plain string so the prompt renders. |
| thread_summary | Write a prompt that asks the agent to summarize a comment thread. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct resource or access mode: single item, batch items, category stories, threaded comments, user profile, latest ID, and recent updates. There is no meaningful overlap that would cause an agent to select the wrong tool.
All tool names follow the same get_* snake_case convention, with clear noun targets. Pluralization is used sensibly to distinguish batch endpoints from singular endpoints.
Seven tools is well-scoped for a read-only Hacker News API client covering items, stories, comments, users, and metadata. Each tool adds distinct value without bloat.
The set covers the core Hacker News API surface: fetching items individually or in bulk, story categories, comment threads, user profiles, latest item ID, and recent updates. No significant dead ends or missing read operations are apparent.