Skip to main content
Glama
enesjakozh
imprvhub

mcp-claude-hackernews

by imprvhub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

MCP クロード・ハッカーニュース

鍛冶屋のバッジ

特徴

  • Hacker Newsの最新記事を閲覧する

  • トップストーリーと最高評価のストーリーを見る

  • ストーリーの詳細を見る

  • 記事のコメントを読む

  • Hacker News のコンテンツを整理して読みやすくする

Related MCP server: MCP Hacker News

デモ

要件

  • Node.js 16以上

  • クロードデスクトップ

  • Hacker News APIにアクセスするためのインターネット接続

インストール

手動でインストールする

  1. このリポジトリをクローンまたはダウンロードします:

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

  1. 依存関係をインストールします:

npm install

  1. プロジェクトをビルドします。

npm run build

MCPサーバーの実行

MCP サーバーを実行するには 2 つの方法があります。

オプション1: 手動で実行する

  1. ターミナルまたはコマンドプロンプトを開きます

  2. プロジェクトディレクトリに移動する

  3. サーバーを直接実行します。

node build/index.js

Claude Desktopの使用中は、このターミナルウィンドウを開いたままにしてください。ターミナルを閉じるまでサーバーは稼働し続けます。

オプション 2: Claude Desktop で自動起動 (通常の使用に推奨)

Claude Desktopは、必要に応じてMCPサーバーを自動的に起動できます。設定手順は次のとおりです。

構成

Claude Desktop の構成ファイルは次の場所にあります。

  • macOS : ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows : %APPDATA%\Claude\claude_desktop_config.json

  • Linux : ~/.config/Claude/claude_desktop_config.json

このファイルを編集して、Hacker News MCPの設定を追加します。ファイルが存在しない場合は作成してください。

{
  "mcpServers": {
    "hackerNews": {
      "command": "node",
      "args": ["ABSOLUTE_PATH_TO_DIRECTORY/mcp-claude-hackernews/build/index.js"]
    }
  }
}

重要: ABSOLUTE_PATH_TO_DIRECTORY 、MCP をインストールした完全な絶対パスに置き換えてください。

  • macOS/Linuxの例: /Users/username/mcp-claude-hackernews

  • Windows の例: C:\\Users\\username\\mcp-claude-hackernews

既に他のMCPを設定している場合は、「mcpServers」オブジェクト内に「hackerNews」セクションを追加するだけです。複数のMCPを設定する例を以下に示します。

{
  "mcpServers": {
    "otherMcp1": {
      "command": "...",
      "args": ["..."]
    },
    "otherMcp2": {
      "command": "...",
      "args": ["..."]
    },
    "hackerNews": {
      "command": "node",
      "args": [
        "ABSOLUTE_PATH_TO_DIRECTORY/mcp-claude-hackernews/build/index.js"
      ]
    }
  }
}

MCP サーバーは、 claude_desktop_config.jsonファイルの設定に基づいて、Claude Desktop が必要とするときに自動的に起動します。

使用法

  1. 設定を変更した後、Claude Desktopを再起動します。

  2. Claudeでは、 hnコマンドを使用してHacker Newsとやり取りします。

  3. MCPサーバーはClaude Desktopによって管理される子プロセスとして実行されます。

利用可能なコマンド

Hacker News MCP は、 hnという単一のツールといくつかのコマンドを提供します。

指示

説明

パラメータ

例

latest

Hacker Newsの最新ニュースを入手

param : オプションの階数（デフォルト: 10、最大: 50）

hn latest --50

top

Hacker Newsのトップストーリーを入手

param : オプションの階数（デフォルト: 10、最大: 50）

hn top --20

best

Hacker Newsから最高の記事を入手

param : オプションの階数（デフォルト: 10、最大: 50）

hn best --30

history

特定のストーリーに関する詳細情報を取得する

param : 必須のストーリーID

hn history --12345678

comments

記事へのコメントをもらう

param : 最後のリストまたはストーリーIDからの必要なインデックス

hn comments --3またはhn comments --12345678

使用例

以下に、クロード氏による Hacker News MCP の使用方法に関するさまざまな例を示します。

直接コマンド:

hn latest --50
hn top --20
hn best --30
hn history --29384756
hn comments --5

自然言語クエリ:

自然言語を使ってMCPと対話することもできます。クロードはこれらのリクエストを解釈し、適切なコマンドを使用します。

  • 「今日のHacker Newsのトップ30記事を見せてください」

  • 「Hacker News の最新 40 件の投稿は何ですか?」

  • 「Hacker Newsのベスト記事20を見たい」

  • 「Hacker News から最近の技術ニュース記事を 30 件取得してもらえますか?」

  • 「Hacker Newsで話題のトップ50を教えてください」

  • 「機械学習に関する Hacker News の記事を 20 件表示してください」

  • 「最新の Hacker News の見出しを 40 件表示してください」

  • 「現在 Hacker News で最も活発な 30 の議論は何ですか?」

  • 「今週最も人気のあるHacker Newsの記事40件を読みたい」

  • 「Hacker Newsのプログラミング記事ベスト20のリストを見せてください」

言語翻訳リクエスト:

Hacker News のコンテンツをさまざまな言語に翻訳するようリクエストできます。

  • 「今日のHacker Newsのトップ30記事をスペイン語で表示してください」

  • 「最新の Hacker News 記事 20 件を取得し、フランス語に翻訳してください」

  • 「Hacker Newsのベスト記事40をドイツ語で見たい」

  • 「最近の Hacker News 記事を日本語に翻訳して 30 件表示してください」

  • 「Hacker Newsのトップ20記事を入手してポルトガル語で発表してください」

トラブルシューティング

「サーバーが切断されました」エラー

Claude Desktop で「MCP Hacker News: サーバーが切断されました」というエラーが表示された場合:

  1. サーバーが実行中であることを確認します:

    • ターミナルを開き、プロジェクトディレクトリからnode build/index.js手動で実行します。

    • サーバーが正常に起動したら、このターミナルを開いたままClaudeを使用します。

  2. 設定を確認してください:

    • claude_desktop_config.jsonの絶対パスがシステムに合っていることを確認してください

    • Windowsのパスに二重のバックスラッシュ（ \\ ）を使用していることを確認してください

    • ファイルシステムのルートからの完全なパスを使用していることを確認してください

  3. 自動起動オプションを試してください:

    • 「自動起動スクリプトの設定」セクションの説明に従って、オペレーティング システムの自動起動スクリプトを設定します。

    • これにより、必要なときにサーバーが常に実行されるようになります。

クロードにツールが表示されない

Hacker News ツールが Claude に表示されない場合は:

  • 設定後、Claude Desktopを再起動してください。

  • Claude Desktop のログで MCP 通信エラーがないか確認します。

  • MCP サーバー プロセスが実行されていることを確認します (手動で実行して確認してください)

  • MCP サーバーが Claude Desktop MCP レジストリに正しく登録されていることを確認します。

サーバーが実行中かどうかを確認しています

サーバーが実行中かどうかを確認するには:

  • Windows : タスクマネージャーを開き、「詳細」タブに移動して「node.exe」を探します。

  • macOS/Linux : ターミナルを開き、 ps aux | grep nodeを実行します。

サーバーが実行中になっていない場合は、手動で起動するか、自動起動の方法を使用します。

貢献

貢献を歓迎します！お気軽にプルリクエストを送信してください。

ライセンス

このプロジェクトは、Mozilla Public License 2.0 に基づいてライセンスされています。詳細については、 LICENSEファイルを参照してください。

関連リンク

Available Tools

6 tools
hn_bestC

Get the best stories from Hacker News

ParametersJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of items to fetch (1-50, default: 10)

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It conveys only that this is a read of stories; it says nothing about ordering semantics ('best' by what ranking?), result freshness, or pagination, which matters most given the hn_top sibling.

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

Conciseness4/5

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

A single front-loaded sentence with zero waste. It is appropriately sized, though its brevity is part of why key distinctions are missing.

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

Completeness3/5

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

For a simple one-parameter list tool this is minimally adequate, and the schema covers the input. However, with no output schema and no annotation coverage, the unresolved 'best' vs 'top' ambiguity and lack of ordering information leave a meaningful gap.

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

Parameters3/5

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

Schema description coverage is 100% and the single 'limit' parameter is fully documented in the schema (range, default), so the baseline of 3 applies. The description adds no additional meaning about the parameter.

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

Purpose3/5

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

States a clear verb+resource ('Get the best stories from Hacker News'), but the sibling hn_top makes 'best' ambiguous — an agent cannot tell from the description how 'best' differs from 'top' or 'latest'. The purpose is understandable but not differentiated from its siblings.

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

Usage Guidelines2/5

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

No guidance on when to choose this over hn_top, hn_latest, or hn_search. There is no statement of context, prerequisites, or exclusions, leaving selection between four similarly-named story-fetching tools to guesswork.

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

hn_commentsB

Get top-level comments for a story (by story ID or index from the last story list)

ParametersJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of items to fetch (1-50, default: 20)
story_idNoThe ID of the story to get comments for
story_indexNoThe index (1-based) of the story from the last fetched list

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. 'Top-level comments' is a useful behavioral nuance (excludes nested replies), but the description omits return format, pagination, whether the call is safe/read-only, and any rate or auth context for a tool that hits an external API.

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

Conciseness4/5

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

A single compact sentence with the resource front-loaded and input modes in a parenthetical. Efficient, though the parenthetical is dense and slightly compressed.

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

Completeness3/5

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

With no output schema and no annotations, the description should explain the return shape and the mutual exclusivity of story_id vs story_index for a 0-required-param tool. It covers purpose adequately but leaves these gaps.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description names story ID and index as inputs but does not clarify that these are alternative selectors or which takes precedence when both are omitted (0 required params).

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

Purpose4/5

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

States a specific verb (Get) and resource (top-level comments for a story), which differentiates it from siblings like hn_story and hn_latest. The parenthetical clarifies input modes but the description doesn't explicitly contrast with siblings.

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

Usage Guidelines3/5

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

The parenthetical implies usage context ('index from the last story list'), suggesting it's meant to be called after a list tool, but no explicit when-to-use or alternatives are stated. Usage is inferred rather than directed.

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

hn_latestB

Get the latest/newest stories from Hacker News

ParametersJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of items to fetch (1-50, default: 10)

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get' implies a read-only retrieval, but the description does not mention authentication, rate limits, pagination, return format, or any other operational behavior.

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

Conciseness5/5

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

The description is a single, front-loaded sentence with no wasted words. It communicates the core purpose immediately and is appropriately sized for a simple retrieval tool.

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

Completeness3/5

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

For a simple tool with one optional parameter and no output schema, the description is minimally adequate. However, it omits any indication of the return shape and does not help the agent choose between this and similar sibling tools like hn_top or hn_best.

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

Parameters3/5

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

The input schema has 100% description coverage, fully documenting the single 'limit' parameter with its default and range. The description itself adds no additional parameter meaning, so the baseline of 3 is appropriate.

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

Purpose4/5

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

The description states a specific verb and resource: getting latest/newest stories from Hacker News. It distinguishes itself somewhat from hn_top and hn_best by emphasizing recency rather than ranking, but it does not explicitly name or differentiate against those sibling tools.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives such as hn_top, hn_best, or hn_search. The agent can infer that it is for recent stories, but no conditions, exclusions, or alternatives are provided.

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

hn_storyA

Get details for a specific story by ID

ParametersJSON Schema
NameRequiredDescriptionDefault
story_idYesThe ID of the story to fetch

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description is the sole source. It indicates a read operation ('get details'), but does not disclose error behavior, rate limits, or response structure. Basic transparency is achieved.

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

Conciseness5/5

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

The description is a single, well-structured sentence with no extraneous words or filler. It is optimally concise.

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

Completeness3/5

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

For a simple one-parameter tool with no output schema, the description provides minimal but sufficient context. It lacks detail on what 'details' includes, which is acceptable for a simple fetch.

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

Parameters3/5

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

Schema coverage is 100% as the only parameter 'story_id' has a description. The description 'by ID' aligns with the parameter, adding no new meaning. Baseline score applies.

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

Purpose5/5

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

The description clearly states the action ('get details'), the resource ('story'), and the identification method ('by ID'). It distinctly differentiates from sibling tools (lists like hn_best, hn_top) which fetch multiple items.

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

Usage Guidelines4/5

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

The description implies usage when a specific story ID is known, but does not explicitly exclude cases like fetching stories in bulk or provide alternatives. Sibling tool names indirectly suggest other use cases.

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

hn_topB

Get the top-ranked stories from Hacker News

ParametersJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of items to fetch (1-50, default: 10)

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing beyond the implied read-only nature of 'Get'. It does not say whether results are live-fetched from the HN API, cached, paginated, or what the return structure looks like for a tool with no output schema.

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

Conciseness5/5

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

A single front-loaded sentence with no filler or redundancy. Every word earns its place, and the core purpose is stated immediately.

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

Completeness3/5

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

For a one-optional-parameter list tool with no output schema and no annotations, the description is minimally adequate: it identifies the resource but not what 'top-ranked' means (score? front page?) or what a returned item contains. Enough to attempt a call, not enough to predict the result.

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

Parameters3/5

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

Schema description coverage is 100% for the single 'limit' parameter, including range and default, so the description need not restate it. The description adds no meaning beyond the schema, which is the expected baseline here.

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

Purpose4/5

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

The description states a specific verb and resource ('Get the top-ranked stories from Hacker News'), which is more informative than the bare name hn_top. However, it offers no differentiation from close siblings like hn_best and hn_latest, leaving 'top-ranked' nearly synonymous with 'best' and forcing the agent to guess which ranking endpoint to use.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this tool over hn_best, hn_latest, or hn_search, and no stated prerequisites or context. The agent must infer selection purely from the tool names.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 5 tool updatesv0.2.0
    • Changedhn_best1 field changed
      • changedInput schema / properties / limit / description
        Previous value: -"Number of stories to fetch (1-50, default: 10)"New value: +"Number of items to fetch (1-50, default: 10)"
    • Changedhn_comments1 field changed
      • addedInput schema / properties / limit
        Added value: +{
+  "default": 20,
+  "description": "Number of items to fetch (1-50, default: 20)",
+  "maximum": 50,
+  "minimum": 1,
+  "type": "number"
+}
    • Changedhn_latest1 field changed
      • changedInput schema / properties / limit / description
        Previous value: -"Number of stories to fetch (1-50, default: 10)"New value: +"Number of items to fetch (1-50, default: 10)"
    • Addedhn_search
    • Changedhn_top1 field changed
      • changedInput schema / properties / limit / description
        Previous value: -"Number of stories to fetch (1-50, default: 10)"New value: +"Number of items to fetch (1-50, default: 10)"
  2. 5 tool updatesv1.0.0
    • First observedhn_best
    • First observedhn_comments
    • First observedhn_latest
    • First observedhn_story
    • First observedhn_top
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.5/5.0

Scored across 6 tools

Disambiguation5/5

hn_latest, hn_top, and hn_best target distinct Hacker News ranking feeds, while hn_search, hn_comments, and hn_story have clearly separate roles. There is no meaningful overlap or ambiguity in purpose.

Naming Consistency5/5

All tools use the same hn_ prefix and snake_case convention. The suffixes vary semantically (feeds, search, comments, story) but the naming pattern is predictable and consistent.

Tool Count5/5

Six tools are well-scoped for a read-only Hacker News server covering feeds, search, story details, and comments. Each tool earns its place without unnecessary duplication.

Completeness4/5

The surface covers the core HN read workflows: latest/top/best feeds, search, story details, and top-level comments. Minor gaps exist, such as nested comment retrieval and dedicated Ask/Show/Jobs feeds, but agents can work around them with search or story IDs.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • MCP Hacker News

    paabloLC
    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
    109 npm
    34
    MIT

  • Hacker News MCP Server

    davidvgilmore
    F
    license
    Not graded
    quality
    D
    maintenance
    Enables AI assistants to fetch top, new, best, Ask HN, Show HN, and job stories, as well as specific posts, comments, and user information from Hacker News through the Model Context Protocol.
    1
    -