Hacker News Companion MCP
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 |
|---|---|
| get_hn_post_formatted_commentsB | Retrieves and formats comments from a Hacker News discussion post for summarization by an LLM. Use the |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly distinct as it is the sole tool available.
Since there is only one tool, naming consistency is inherently perfect. The tool name follows a clear verb_noun pattern (get_hn_post_formatted_comments), which would be consistent if more tools existed.
A single tool is too few for a server named 'Hacker News Companion MCP', which suggests broader functionality. The tool only handles comment retrieval and formatting, leaving obvious gaps like fetching posts, searching, or user interactions, making the scope feel incomplete.
The tool set is severely incomplete for a Hacker News companion. It only covers retrieving and formatting comments for summarization, missing core operations such as getting posts, listing top stories, or user management, which are essential for the domain.