Skip to main content
Glama
GeorgeNance

Hacker News MCP Server

by GeorgeNance

📰 Hacker News MCP Server

CI License: MIT

A Model Context Protocol (MCP) server that provides tools to fetch and interact with Hacker News content. This server enables AI assistants to access real-time Hacker News data including top stories, story details, comments, and search functionality.

🚀 Features

🛠️ Available Tools

  • get_top_stories - Fetch the latest top stories from Hacker News

    • Configurable count (1-100 stories)

    • Optional text content inclusion

    • Returns story metadata including title, URL, score, author, and comment count

  • get_story_details - Get detailed information about a specific story

    • Fetch complete story metadata

    • Optional comment inclusion with threaded structure

    • Optional markdown content extraction from linked articles

  • get_story_comments - Retrieve popular comments for a story

    • Configurable minimum score filtering

    • Adjustable comment thread depth (1-10 levels)

    • Limit number of comments returned (1-100)

    • Formatted as readable text with thread structure

  • search_stories - Search recent stories by keywords

    • Search through story titles, content, and URLs

    • Configurable time range (1-168 hours)

    • Limit results (1-50 stories)

Related MCP server: HackerNews MCP Server

📋 Prerequisites

  • Node.js 18+

  • npm or yarn

  • An MCP-compatible client (like Claude Desktop)

🔧 Installation

1. Clone the repository

git clone https://github.com/yourusername/hackernews-mcp.git
cd hackernews-mcp

2. Install dependencies

npm install

3. Build the server

npm run build

🎯 Usage

With Claude Desktop

Add the server to your Claude Desktop configuration:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "hackernews-mcp": {
      "command": "node",
      "args": ["/path/to/hackernews-mcp/build/index.js"]
    }
  }
}

With Other MCP Clients

The server communicates via stdio and can be used with any MCP-compatible client:

node build/index.js

🔍 Example Usage

Once connected, you can ask your AI assistant things like:

  • "What are the top stories on Hacker News today?"

  • "Get details about Hacker News story 12345678"

  • "Show me comments for that viral AI story"

  • "Search for recent stories about TypeScript"

🛠️ Development

Build the project

npm run build

Watch mode for development

npm run watch

Lint and format the code

npm run lint
npm run format

Run the MCP Inspector

For debugging and testing:

npm run inspector

This will start the MCP Inspector, providing a web interface to test the server's tools and inspect the communication.

📦 Code Quality & Contributing

  • Code Quality:
    This project enforces code quality and style using ESLint and Prettier. All code is checked in CI (GitHub Actions) and must pass linting and formatting before merging.

  • Type Safety:
    All tool handlers use explicit type guards for runtime argument validation and robust TypeScript types.

  • CI/CD:
    Every push and pull request runs the full build, lint, and (future) test suite via GitHub Actions.

  • How to Contribute:

    1. Fork the repository

    2. Create a feature branch (git checkout -b feature/amazing-feature)

    3. Commit your changes (git commit -m 'Add amazing feature')

    4. Run npm run lint and npm run format before pushing

    5. Push to the branch (git push origin feature/amazing-feature)

    6. Open a Pull Request

📚 API Reference

get_top_stories

{
  count?: number;        // Number of stories (1-100, default: 30)
  include_text?: boolean; // Include story text content (default: false)
}

get_story_details

{
  story_id: number;           // Required: HN story ID
  include_comments?: boolean; // Include comments (default: false)
  include_markdown?: boolean; // Extract article as markdown (default: false)
}

get_story_comments

{
  story_id: number;    // Required: HN story ID
  min_score?: number;  // Minimum comment score (default: 1)
  max_depth?: number;  // Max thread depth (1-10, default: 3)
  limit?: number;      // Max comments (1-100, default: 20)
}

search_stories

{
  query: string;              // Required: Search keywords
  limit?: number;             // Max results (1-50, default: 20)
  time_range_hours?: number;  // Hours to search back (1-168, default: 24)
}

🏗️ Architecture

The server is built with:

  • TypeScript for type safety and developer experience

  • @modelcontextprotocol/sdk for MCP protocol implementation

  • axios for HTTP requests to Hacker News API

  • jsdom and turndown for HTML to Markdown conversion

  • private-ip for security (blocks private IP access)

Key Components

  • src/index.ts - Main server implementation with tool handlers

  • src/fetcher.ts - Utility class for fetching and converting web content

  • build/ - Compiled JavaScript output (auto-generated)

🔒 Security

  • Blocks requests to private IP addresses to prevent local network access

  • Rate limiting through Hacker News API natural limits

  • Input validation for all tool parameters

  • Error handling and graceful degradation

📜 License

This project is licensed under the MIT License - see the LICENSE file for details.

🙏 Acknowledgments

📞 Support

If you encounter any issues or have questions:

  1. Check the Issues page

  2. Use the MCP Inspector for debugging: npm run inspector

  3. Create a new issue with detailed information about your problem


Made with ❤️ for the MCP community

Available Tools

1 tool
get_top_hackernews_storiesD
ParametersJSON Schema
NameRequiredDescriptionDefault
countNo

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

TDQS

D1.8/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools. The single tool has a clear, distinct purpose of retrieving top stories from Hacker News.

Naming Consistency5/5

With only one tool, naming consistency is inherently perfect. The tool name follows a clear verb_noun pattern (get_top_hackernews_stories) that would be appropriate if more tools were added.

Tool Count2/5

A single tool is too few for a server named 'Hacker News MCP Server', which suggests broader functionality. While get_top_hackernews_stories is useful, the server lacks tools for other common Hacker News operations like getting new stories, best stories, or individual items.

Completeness2/5

The server is severely incomplete for the Hacker News domain. It only provides access to top stories, missing essential operations like retrieving new stories, best stories, individual items, comments, user profiles, or search functionality that would be expected from a Hacker News API.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • A
    license
    A
    quality
    D
    maintenance
    A Model Context Protocol server that enables AI tools like Claude and Cursor to fetch and interact with live Hacker News data (posts, comments, users) via standardized MCP endpoints.
    11
    119
    33
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    A server that enables AI assistants to access, analyze, and understand HackerNews content through standardized Model Context Protocol interfaces, providing tools for searching posts, analyzing users, and tracking trending topics.
    5
    8
    MIT
  • A
    license
    A
    quality
    C
    maintenance
    MCP server enabling AI agents to interact with Hacker News, including fetching full comment trees with depth control, searching stories and comments, and retrieving user profiles.
    6
    5
    MIT

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GeorgeNance/hackernews-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server