HackerNews MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_postsA | Search HackerNews posts by keywords with advanced filtering options. Supports filtering by content type (story, comment, poll, etc.), author, date ranges, points thresholds, and comment counts. Returns paginated results with metadata. Default sort is by relevance, but can sort chronologically with sortByDate=true. |
| get_front_pageA | Retrieve current HackerNews front page posts. Returns the posts currently featured on the HN front page, ordered by rank. Supports pagination to browse through all front page items. Front page typically contains 30 posts per page (matches the HN website). |
| get_postA | Retrieve full details of a specific HackerNews post by its ID. Returns the complete post data including title, URL, author, points, and the entire comment tree with nested replies. Comments are returned in hierarchical structure preserving parent-child relationships. Includes metadata like total comment count and nesting depth. |
| get_userA | Retrieve HackerNews user profile information by username. Returns user metadata including karma score, account creation date, and about/bio text. Includes computed fields like account age in years and average karma per year to provide context about user activity and reputation. |
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: get_front_page retrieves the front page, get_post fetches a specific post, get_user gets user profiles, and search_posts performs keyword searches. There is no overlap or ambiguity between these functions, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern (get_front_page, get_post, get_user, search_posts) using snake_case. This uniformity enhances readability and predictability, allowing agents to easily understand the action and target of each tool.
With 4 tools, this server is well-scoped for a HackerNews interface. Each tool serves a distinct and essential function (browsing front page, viewing posts, checking users, and searching), providing a complete yet manageable set without unnecessary complexity or bloat.
The tool set covers core HackerNews interactions effectively: reading posts (front page and specific), user profiles, and searching. A minor gap is the lack of write operations (e.g., posting or commenting), but this is reasonable for a read-only server focused on data retrieval, and agents can still perform most common tasks.