mediawiki-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchB | Search for a wiki page. The shorter the request, the better, preferably containing only the main term to be searched. Args: query: The query to search for limit: The number of results to return Returns: A list of pages that match the query |
| get_pageB | Get a page from mediawiki.org Args: title: The title of the page to get, which can be found in title field of the search results Returns: The page content |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: get_page retrieves specific page content by title, while search finds pages matching a query. There is no overlap in functionality, making it easy for an agent to select the correct tool based on the task.
Both tools follow a consistent verb_noun pattern (get_page and search, where search implies 'search_pages'). The naming is simple, predictable, and uses snake_case uniformly, providing clear readability.
With only 2 tools, the server feels thin for a MediaWiki domain, lacking essential operations like creating, updating, or deleting pages. While get_page and search cover basic retrieval, the scope is incomplete, making it borderline too few for practical use.
The tool surface is severely incomplete for a MediaWiki server, missing core CRUD operations (e.g., create_page, update_page, delete_page) and other common actions like listing categories or handling user interactions. This will likely cause agent failures in broader workflows.