Skip to main content
Glama
kongyo2

MediaWiki Syntax MCP Server

by kongyo2
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

MediaWiki Syntax MCP Server

A comprehensive MediaWiki syntax documentation server built with FastMCP.

This MCP server provides complete MediaWiki markup syntax documentation by dynamically fetching and consolidating information from official MediaWiki help pages. It enables LLMs to access up-to-date and comprehensive MediaWiki syntax information.

Features

  • Comprehensive Coverage: Fetches syntax information from multiple official MediaWiki help pages

  • Dynamic Updates: Always provides current documentation from MediaWiki.org

  • Clean Content: Extracts only the essential syntax information, removing navigation and metadata

  • Structured Output: Organizes syntax information by categories (formatting, links, tables, etc.)

Related MCP server: WikiMCP

Development

To get started, clone the repository and install the dependencies.

git clone https://github.com/kongyo2/mediawiki-syntax-mcp.git
cd mediawiki-syntax-mcp
npm install
npm run dev

Usage

Start the server

If you simply want to start the server, you can use the start script.

npm run start

However, you can also interact with the server using the dev script.

npm run dev

This will start the server and allow you to interact with it using CLI.

Available Tools

The server provides one main tool:

  • get-mediawiki-syntax: Retrieves comprehensive MediaWiki syntax documentation

    • format (optional): "complete" for full documentation (default) or "summary" for condensed version

Testing

npm run test

The tests verify that the server module can be properly imported and initialized.

Linting

Having a good linting setup reduces the friction for other developers to contribute to your project.

npm run lint

This boilerplate uses Prettier, ESLint and TypeScript ESLint to lint the code.

Formatting

Use npm run format to format the code.

npm run format

MediaWiki Syntax Coverage

This server fetches syntax documentation from the following official MediaWiki help pages:

  • Text Formatting: Basic text formatting, headings, lists, and markup

  • Links: Internal links, external links, interwiki links, and piped links

  • Tables: Table creation and formatting syntax

  • Images and Media: Image embedding, sizing, and media file syntax

  • Templates: Template usage, parameters, and transclusion

  • Categories: Category assignment and organization

  • Magic Words: Variables, parser functions, and behavior switches

  • Citations and References: Reference and citation syntax

Configuration

The server is designed to work out of the box with no configuration required. It dynamically fetches content from MediaWiki.org using the MediaWiki API, similar to the approach used in wikipedia-mcp.

Available Tools

1 tool
get-mediawiki-syntaxA
Read-only

Retrieve comprehensive MediaWiki syntax documentation by dynamically fetching from official MediaWiki help pages. This provides complete and up-to-date markup syntax for all MediaWiki features including formatting, links, tables, images, templates, categories, magic words, and citations.

ParametersJSON Schema
NameRequiredDescriptionDefault
formatNoFormat of the documentation - 'complete' for full syntax guide (default), 'summary' for condensed version

TDQS

A4/5.0
Behavior4/5

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

Annotations indicate readOnlyHint=true and openWorldHint=true, which the description does not contradict. The description adds valuable behavioral context beyond annotations by specifying that it 'dynamically fetches' from external sources, ensuring 'complete and up-to-date' information, which helps the agent understand real-time data retrieval and reliability aspects.

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

Conciseness5/5

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

The description is front-loaded with the core purpose in the first sentence, followed by specifics in a second sentence. Every sentence adds essential information (e.g., dynamic fetching, scope of features) without redundancy, making it highly efficient and well-structured.

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 moderate complexity (external data fetching), rich annotations (readOnlyHint, openWorldHint), and no output schema, the description is largely complete. It covers purpose, behavior, and scope adequately, though it could slightly enhance completeness by mentioning potential limitations like network dependencies or response formats.

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

Parameters3/5

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

The input schema has 100% description coverage, clearly documenting the 'format' parameter with its enum values and default. The description does not add any parameter-specific details beyond what the schema provides, so it meets the baseline score of 3 for high schema coverage without extra semantic value.

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 the tool's purpose with specific verbs ('Retrieve comprehensive MediaWiki syntax documentation') and resources ('from official MediaWiki help pages'), and it enumerates the scope of content covered ('formatting, links, tables, images, templates, categories, magic words, and citations'). With no sibling tools, this level of detail is excellent.

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?

The description implies usage for obtaining up-to-date MediaWiki syntax, but it does not provide explicit guidance on when to use this tool versus alternatives (e.g., other documentation sources) or any prerequisites. Since there are no sibling tools, the lack of comparative guidance is less critical, but no explicit when/when-not instructions are given.

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

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.9/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clear and distinct purpose focused on retrieving MediaWiki syntax documentation.

Naming Consistency5/5

The single tool name 'get-mediawiki-syntax' follows a clear verb_noun pattern, and with only one tool, consistency is inherently perfect as there are no other names to compare against.

Tool Count2/5

A single tool is too few for a server that claims to cover MediaWiki syntax comprehensively. While the tool provides documentation, typical MediaWiki operations like parsing, rendering, or editing are missing, making the scope feel incomplete and limiting for agents.

Completeness2/5

The server is severely incomplete for its apparent purpose. It only offers retrieval of syntax documentation, lacking essential operations such as converting to/from MediaWiki syntax, validating markup, or interacting with MediaWiki content, which are core to the domain.

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

  • mediawiki-mcp-server

    shiquda
    F
    license
    B
    quality
    C
    maintenance
    A MCP server that allows you to search and retrieve content on any wiki site using MediaWiki with LLMs 🤖. wikipedia.org, fandom.com, wiki.gg and more sites using Mediawiki are supported!
    2
    26

  • WikiMCP

    raydeStar
    F
    license
    Not graded
    quality
    D
    maintenance
    An MCP server for Wiki.js projects that enables full-text search, page retrieval, and page management capabilities. It allows LLMs to interact with wiki content through specialized tools for searching, listing, and creating pages.

  • mcp-mediawiki-crunchtools

    crunchtools
    A
    license
    B
    quality
    C
    maintenance
    A secure MCP server for interacting with MediaWiki instances, allowing users to search, read, create, and manage wiki content like pages, categories, and files. It supports both public and private wikis with comprehensive authentication for full read and write operations.
    19
    AGPL 3.0

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/kongyo2/MediaWiki-Syntax-MCP'

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