MCP Server with Wikipedia Article Tool

Created By
codingaslua year ago
A lightweight implementation of the Model Context Protocol (MCP) server using Server-Sent Events. Features a Wikipedia article parser that converts content to Markdown format. Demonstrates client-server MCP communication over HTTP.
Overview

What is MCP Server with Wikipedia Article Tool?

This project is a lightweight implementation of the Model Context Protocol (MCP) server that utilizes Server-Sent Events (SSE) to facilitate client-server communication. It includes a tool for fetching Wikipedia articles and converting their content into Markdown format.

How to use MCP Server with Wikipedia Article Tool?

To use this project, clone the repository, install the required dependencies, and start the server. You can then use the client to fetch Wikipedia articles and receive them in Markdown format.

Key features of MCP Server with Wikipedia Article Tool?

  • Implementation of MCP server using FastMCP
  • Client-server communication via Server-Sent Events (SSE)
  • Tool for fetching Wikipedia articles
  • Conversion of HTML content to Markdown format

Use cases of MCP Server with Wikipedia Article Tool?

  1. Fetching and converting Wikipedia articles for documentation purposes.
  2. Integrating Wikipedia content into applications that require Markdown formatting.
  3. Demonstrating client-server communication using the MCP protocol.

FAQ from MCP Server with Wikipedia Article Tool?

  • What programming language is used for this project?

The project is implemented in Python 3.8 and above.

  • How do I start the server?

You can start the server by running python server.py after installing the dependencies.

  • What endpoints are available?

The server provides /sse for SSE connections and /messages/ for handling incoming POST messages.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
codingaslu
Star
0
Language
Python
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