Skip to main content
Glama
tomwojcik

hn-mcp

by tomwojcik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_comment_treeA

Fetch a specific comment and its reply subtree.

Use this to dive into a branch after scanning top-level comments
with get_thread(depth=1).

Args:
    comment_id: The HN comment ID.
    depth: How many levels of replies to include below this comment.
        0 = this comment only (with reply_count).
        N = N levels of replies.
        -1 = full subtree (default).
get_storiesA

Browse HN stories by category. Returns metadata only (no comments).

Args:
    category: One of: top, new, ask_hn, show_hn.
    count: Number of stories to return (default 20, max 100).
get_threadA

Fetch a story and its comment tree from Hacker News.

Args:
    story_id: The HN story ID.
    depth: How many levels of comment nesting to include.
        0 = story metadata only, no comments.
        1 = top-level comments only (each includes reply_count).
        2 = top-level + their direct replies.
        N = N levels deep.
        -1 = entire tree, no limits.
get_userB

Fetch a Hacker News user profile.

Args:
    username: The HN username.
search_commentsA

Full-text search for HN comments.

Args:
    query: Search terms.
    sort_by: "relevance" or "date".
    story_id: Optional — only search comments on this story.
    author: Optional — only search comments by this author.
    count: Results per page (default 20, max 100).
    page: Page number, 0-indexed.
search_storiesA

Full-text search for HN stories.

Args:
    query: Search terms.
    sort_by: "relevance" or "date".
    count: Results per page (default 20, max 100).
    page: Page number, 0-indexed.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.2/5.0

Scored across 6 tools

Disambiguation5/5

Each tool addresses a distinct purpose: browsing story lists, fetching a story with comments, drilling into a comment subtree, retrieving user profiles, and searching stories/comments. No overlap in core functionality.

Naming Consistency5/5

All retrieval tools follow a consistent 'get_' prefix, while search tools use 'search_', making the naming pattern predictable and easy to navigate.

Tool Count5/5

Six tools cover the essential read-only operations for Hacker News without excessive granularity or unnecessary overlap, which is well-scoped for the domain.

Completeness5/5

The toolkit provides comprehensive coverage for browsing HN: story feeds, story/comment retrieval with configurable depth, user profiles, and full-text search for both stories and comments. No obvious gaps for a read-only client.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources