Interact with Wizzypedia through the MediaWiki API, supporting both read-only and authenticated operations.
This is a Model Context Protocol (MCP) server for interacting with the Wizzpedia APIs, designed to work with MCP-enabled editors like Cursor or Claude Desktop.
This means you can query (or write) to the Wizzypedia from any MCP enabled tool.
User: Download the wikitext of the "Dotta" page into a Dotta.wiki file in this repo
AI: I'll help you download the wikitext content of the "Dotta" page and save it to a file. Let me break this down into steps: First, I'll fetch the wikitext content of the "Dotta" page: ...
// Dotta.wiki page created
// Now you can edit Dotta.wiki locally
User: Now update the Dotta page with the contents of this file
AI: I've successfully updated the Dotta page on the wiki with the contents from our local file. The update was successful and created a new revision (ID: 42157). The content includes all the sections from our local file, including the introduction, The Great Dotta Burning section, and the gallery of images.
The server can run in two modes:
Authentication credentials are only required if you need to perform write operations (creating/updating pages).
You can configure the MCP server in either read-only or authenticated mode. Choose the configuration that matches your needs:
This configuration allows read operations only (search, view pages, etc).
For Cursor (~/.cursor/mcp.json
):
{ "mcpServers": { "wizzypedia": { "command": "npx", "args": ["-y", "wizzypedia-mcp-server"] } } }
For Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json
on macOS or %APPDATA%\Claude\claude_desktop_config.json
on Windows):
This configuration enables both read and write operations (create/update pages).
{ "mcpServers": { "wizzypedia": { "command": "npx", "args": [ "-y", "wizzypedia-mcp-server", "--login", "your-username", "--password", "your-password" ] } } }
The server provides the following MCP tools:
Read-only tools (no authentication required):
Write tools (authentication required):
Once the server is running, you can connect to it from Cursor or another MCP-compatible client. This allows you to:
npm install npm run build
Run the server in read-only mode:
node dist/index.js
node dist/index.js --api-url="https://en.wikipedia.org/w/api.php"
npx wizzypedia-mcp-server
Run with authentication for write access:
export MEDIAWIKI_API_URL="https://en.wikipedia.org/w/api.php" export MEDIAWIKI_USERNAME="YourUsername" export MEDIAWIKI_PASSWORD="YourPassword" node dist/index.js
node dist/index.js --api-url="https://en.wikipedia.org/w/api.php" --login="YourUsername" --password="YourPassword"
npx wizzypedia-mcp-server --login YourUsername --password YourPassword
MIT
A GitHub Action that functions as a Slack MCP server, enabling secure image downloads and integrations with Slack.
Sends emails using the Resend API. Requires a Resend API key.
An AI-to-AI consultation system for complex problem-solving and reasoning, using OpenRouter for model access.
Interact with the Ghost blogging platform using the Model Context Protocol (MCP) with Server-Sent Events (SSE) support.
An IMAP Model Context Protocol (MCP) server to expose IMAP operations as tools for AI assistants.
Simple MCP Server to enable a human-in-the-loop workflow in tools like Cline and Cursor.
An MCP server for seamless integration with the Kick.com API.
An MCP server for sending emails via the Postmark service, configured through environment variables.
A server for interacting with Telegram via the MTProto API, requiring API credentials.
Connect to any function, any language, across network boundaries using AgentRPC.