Geeknews Mcp Server

Created By
the0807a year ago
Overview

what is Geeknews MCP Server?

Geeknews MCP Server is a Model Context Protocol (MCP) server that fetches articles from GeekNews. It is implemented in Python and utilizes BeautifulSoup for web scraping.

how to use Geeknews MCP Server?

To use the Geeknews MCP Server, you can install it via Smithery and configure the MCP settings to include the server information. You can also clone the repository and set up a local environment to run the server.

key features of Geeknews MCP Server?

  • Fetch articles from GeekNews with specified types (top, new, ask, show) and number of articles.
  • Retrieve weekly news with detailed information including title, ID, and item list.
  • Provides a structured response with article details such as title, URL, points, author, time, comment count, and ranking.

use cases of Geeknews MCP Server?

  1. Automating the retrieval of the latest news articles from GeekNews.
  2. Integrating with other applications to provide news updates.
  3. Analyzing trends in news articles over time.

FAQ from Geeknews MCP Server?

  • What programming language is used for the server?

The server is implemented in Python.

  • How do I install the server locally?

You can clone the repository from GitHub and follow the setup instructions provided in the documentation.

  • What dependencies are required?

The server requires Python and the BeautifulSoup library for web scraping.

Server Config

{
  "mcpServers": {
    "geeknews-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@smithery/cli@latest",
        "run",
        "@the0807/geeknews-mcp-server",
        "--key",
        ""
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
the0807
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago