Skip to main content
Glama
progamesigner

Wikipedia MCP Server

by progamesigner
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Wikipedia MCP Server

A Model Context Protocol server that provides capabilities to query Wikipedia. This server enables LLMs to get information from Wikipedia.

Available Tools

  • search - Search keyword on Wikipedia.

    • Required arguments:

      • keyword (string): The search keyword

      • language (string): The language

  • fetch - Fetch Wikipedia page content.

    • Required arguments:

      • id (integer): The pade ID

      • language (string): The language

Related MCP server: Wikipedia MCP Server

Installation

Using uv (recommended)

When using uv no specific installation is needed. We will use uvx to directly run wikipedia-mcp.

Using PIP

Alternatively you can install wikipedia-mcp via pip:

pip install wikipedia-mcp-server

After installation, you can run it as a script using:

python -m wikipedia_mcp

Configurations

Using uvx

{
  "mcpServers": {
    "wikipedia-mcp": {
      "command": "uvx",
      "args": [
        "wikipedia-mcp-server@latest"
      ]
    }
  }
}

Using docker

{
  "mcpServers": {
    "wikipedia-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/progamesigner/wikipedia-mcp:latest"
      ]
    }
  }
}

Using pip installation

{
  "mcpServers": {
    "wikipedia-mcp": {
      "command": "python",
      "args": [
        "-m",
        "wikipedia_mcp"
      ]
    }
  }
}

Build

Docker build:

docker build -t wikipedia-mcp .

Available Tools

2 tools
fetchA

Fetch the content of a Wikipedia page by its ID in a specified language.

This function retrieves the full HTML content of a Wikipedia page by its page ID. It uses the MediaWiki API to fetch the content and returns it as a string. The content is normalized to ensure consistent Unicode representation.

:param id: The page ID of the Wikipedia article to fetch. :param language: The language of the Wikipedia article (e.g., 'en' for English). :return: The content of the article as a string, or None if not found.

:raises KeyError: If the 'parse' or 'text' keys are not present in the response. :raises httpx.HTTPStatusError: If the request fails or returns an error status.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesThe page ID to fetch content for
languageYesThe language to fetch in

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description discloses key behavioral traits: uses MediaWiki API, returns string or None, raises specific exceptions. No annotations are provided, so this is sufficient. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with docstring sections, but slightly verbose. It could be more concise while retaining all information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (2 params, no output schema), the description covers inputs, output, and errors adequately. It mentions return value and exceptions, leaving no major gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds value by explaining parameter roles in context (MediaWiki API, normalization). This goes beyond the schema's own descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it fetches content of a Wikipedia page by ID in a specified language. It distinguishes from sibling 'search' by specifying the exact action and parameters.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the description (when you have a page ID), but there is no explicit guidance on when to use this tool over alternatives like 'search', nor any when-not-to-use advice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 2 tool updatesv1.0.1
    • First observedfetch
    • First observedsearch
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.5/5.0
Disambiguation5/5

The tools have clearly distinct purposes: search finds pages by keyword and returns a list, while fetch retrieves the full content of a specific page by its ID. There is no functional overlap.

Naming Consistency5/5

Both tool names are single-word verbs ('fetch', 'search') that accurately describe their actions. They follow a consistent simple verb pattern without mixing conventions.

Tool Count3/5

With only 2 tools, the server feels minimal for a Wikipedia MCP server. While the core operations (search and fetch by ID) are covered, 2 tools is on the low side for typical server scopes.

Completeness2/5

The server lacks several obvious operations, such as fetching a page by title directly (requiring a search then fetch), retrieving random articles, or accessing page summaries. This creates a notable gap in the tool surface.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • wikipedia-mcp

    Rumblingb
    A
    license
    Not graded
    quality
    F
    maintenance
    Enables AI agents to search, read, and explore Wikipedia articles via tools like summaries, categories, and random articles, with no API keys required.
    1
    MIT

  • Wikipedia MCP Server

    scotthelm
    A
    license
    A
    quality
    D
    maintenance
    Enables AI assistants to access Wikipedia content, search articles, retrieve historical events, and fetch images through the Wikipedia API.
    4
    31
    1
    MIT

  • Wikipedia MCP Server

    OriShmila
    F
    license
    Not graded
    quality
    D
    maintenance
    Provides access to Wikipedia through 10 tools including search, article retrieval, summarization, and fact extraction, with multi-language support and robust error handling.
    -

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/progamesigner/wikipedia-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server