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. 이 저장소를 복제하거나 다운로드하세요:

지엑스피1

  1. 종속성 설치:

npm install

  1. 프로젝트를 빌드하세요:

npm run build

MCP 서버 실행

MCP 서버를 실행하는 방법은 두 가지가 있습니다.

옵션 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

  • 윈도우 : %APPDATA%\Claude\claude_desktop_config.json

  • 리눅스 : ~/.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

사용 예

다음은 Claude와 함께 Hacker News MCP를 사용하는 방법에 대한 다양한 예입니다.

직접 명령:

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

자연어 쿼리:

자연어를 사용하여 MCP와 상호 작용할 수도 있습니다. Claude는 이러한 요청을 해석하고 적절한 명령을 사용합니다.

  • "오늘 Hacker News의 상위 30개 기사를 보여주세요"

  • "해커 뉴스에 올라온 최신 게시물 40개는 뭐예요?"

  • "해커뉴스의 베스트 기사 20개를 보고 싶어요"

  • "해커 뉴스에서 최근 기술 뉴스 기사 30개를 가져와 주시겠어요?"

  • "해커 뉴스에서 가장 인기 있는 50개 주제는 뭐예요?"

  • "머신 러닝에 관한 해커 뉴스 기사 20개를 보여주세요"

  • "최근 해커 뉴스 헤드라인 40개를 보여주세요"

  • "현재 Hacker News에서 가장 활발하게 논의되고 있는 30개 토론은 무엇입니까?"

  • "이번 주 가장 인기 있는 해커 뉴스 기사 40개를 읽어보고 싶습니다."

  • "해커 뉴스에서 가장 좋은 프로그래밍 기사 20개를 보여주세요"

언어 번역 요청:

Hacker News 콘텐츠를 다양한 언어로 번역해 달라고 요청할 수 있습니다.

  • "오늘 Hacker News의 상위 30개 기사를 스페인어로 보여주세요"

  • "최신 해커 뉴스 게시물 20개를 받아 프랑스어로 번역하세요"

  • "독일어로 된 Hacker News의 베스트 기사 40개를 보고 싶습니다."

  • "일본어로 번역된 최근 해커 뉴스 기사 30개를 보여주세요"

  • "해커 뉴스의 상위 20개 기사를 포르투갈어로 보여주세요"

문제 해결

"서버 연결 끊김" 오류

Claude Desktop에서 "MCP Hacker News: 서버 연결 끊김" 오류가 표시되는 경우:

  1. 서버가 실행 중인지 확인하세요 .

    • 터미널을 열고 프로젝트 디렉토리에서 node build/index.js 수동으로 실행하세요.

    • 서버가 성공적으로 시작되면 이 터미널을 열어둔 채로 Claude를 사용하세요.

  2. 구성을 확인하세요 :

    • claude_desktop_config.json 의 절대 경로가 시스템에 맞는지 확인하세요.

    • Windows 경로에 이중 백슬래시( \\ )를 사용했는지 다시 한 번 확인하세요.

    • 파일 시스템의 루트에서 전체 경로를 사용하고 있는지 확인하세요.

  3. 자동 시작 옵션을 시도해 보세요 .

    • "자동 시작 스크립트 설정" 섹션에 설명된 대로 운영 체제에 대한 자동 시작 스크립트를 설정하세요.

    • 이렇게 하면 필요할 때 서버가 항상 실행되도록 할 수 있습니다.

Claude에 도구가 나타나지 않음

Claude에 Hacker News 도구가 나타나지 않는 경우:

  • 구성 후 Claude Desktop을 다시 시작했는지 확인하세요.

  • MCP 통신 오류가 있는지 Claude Desktop 로그를 확인하세요.

  • 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
    -