MediaWiki MCP adapter

Created By
lucamauria year ago
A custom Model Context Protocol (MCP) adapter for interacting with MediaWiki and WikiBase APIs. This adapter allows you to fetch and edit MediaWiki pages programmatically using the MCP framework.
Overview

What is MediaWiki MCP Adapter?

MediaWiki MCP Adapter is a custom Model Context Protocol (MCP) adapter designed for interacting with MediaWiki and WikiBase APIs, allowing users to programmatically fetch and edit MediaWiki pages.

How to use MediaWiki MCP Adapter?

To use the MediaWiki MCP Adapter, clone the repository, install the dependencies, configure the adapter with your MediaWiki and WikiBase API endpoints, and start the MCP server.

Key features of MediaWiki MCP Adapter?

  • Fetch the content of a MediaWiki page.
  • Edit a MediaWiki page with new content and an optional summary.
  • Configurable API base URLs for different MediaWiki and WikiBase instances.

Use cases of MediaWiki MCP Adapter?

  1. Automating the retrieval of content from MediaWiki pages.
  2. Programmatically updating MediaWiki pages with new information.
  3. Integrating MediaWiki content into other applications or services.

FAQ from MediaWiki MCP Adapter?

  • What are the requirements to use the MediaWiki MCP Adapter?

You need Node.js (v16 or later) and a MediaWiki instance with API access enabled.

  • Can I configure the adapter for different MediaWiki instances?

Yes! You can set custom API base URLs for different MediaWiki and WikiBase instances.

  • Is there any testing implemented in the project?

Currently, no tests are implemented, but you can add tests in the test directory.

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

Recommend Servers

View All
Payai X402 Tools

an hour ago
Payai X402 Tools

an hour ago
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.

a day ago