Serveur MCP Wikimedia Enterprise

Created By
Seven-94a year ago
Model Context Protocol (MCP) server made for interacting with Wikimedia APIs
Overview

What is Wikimedia API MCP?

Wikimedia API MCP is a Model Context Protocol (MCP) server designed for interacting with Wikimedia APIs, allowing LLMs and assistants to retrieve content from Wikipedia and other Wikimedia projects.

How to use Wikimedia API MCP?

To use the server, clone the repository, set up a virtual environment, install dependencies, and configure your Wikimedia Enterprise credentials. Start the server and integrate it with an MCP client to access its functionalities.

Key features of Wikimedia API MCP?

  • get_article: Retrieve a complete article by its title via the Wikimedia Enterprise API.
  • list_projects: List all available projects in the Wikimedia Enterprise API.
  • search_articles: Search for articles containing a specific term via the public MediaWiki API.

Use cases of Wikimedia API MCP?

  1. Accessing Wikipedia articles programmatically.
  2. Integrating Wikipedia content into applications or services.
  3. Conducting research using data from Wikimedia projects.

FAQ from Wikimedia API MCP?

  • What are the prerequisites for using this project?

You need Python 3.11 or higher and a Wikimedia Enterprise account for certain functionalities.

  • How do I configure my credentials?

You can set your credentials in a .env file or through environment variables.

  • Is there a way to test the server locally?

Yes! You can start the server locally and connect it with an MCP client to test its functionalities.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Seven-94
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