Wikimedia MCP Server

Created By
privetina year ago
An MCP server for interacting with Wikimedia APIs. Access Wikipedia and other Wikimedia project content programmatically.
Overview

what is Wikimedia MCP Server?

Wikimedia MCP Server is a Model Context Protocol (MCP) server designed for interacting with Wikimedia APIs, allowing users to access Wikipedia and other Wikimedia project content programmatically using natural language queries.

how to use Wikimedia MCP Server?

To use the server, set up the required configurations and utilize the provided tools to perform actions such as searching for content, retrieving page details, and accessing featured content.

key features of Wikimedia MCP Server?

  • Full-text search across Wikimedia page content
  • Autocomplete suggestions for page titles
  • Retrieval of page content, title, URL, and metadata
  • Access to different language versions of pages
  • Fetching featured articles and historical events

use cases of Wikimedia MCP Server?

  1. Programmatically searching for articles on specific topics.
  2. Retrieving detailed information about Wikipedia pages.
  3. Accessing historical events and featured content for educational purposes.

FAQ from Wikimedia MCP Server?

  • Can I access content in multiple languages?

Yes! The server supports retrieving content in various languages.

  • Is there a limit on the number of requests I can make?

Yes, rate limiting is handled by the Wikimedia API to ensure fair usage.

  • What programming language is required to use this server?

The server requires Python 3.12 or higher.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
privetin
Star
-
Language
-
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago