Wikipedia APIとのシームレスな連携を実現するMCPサーバー。このツールを使えば、LLMを使ってWikipediaコンテンツを検索・取得できます🤖！
https://github.com/user-attachments/assets/b5d9c5f3-a60e-48ea-8b4b-f1a7524d4fbb
🔍 カスタマイズ可能な wiki サイトで wiki ページを検索します。例: wikipedia.org、fandom.com、wiki.gg など!
📖 詳細なページコンテンツを取得する
Related MCP server: mediawiki-mcp-server
デバイスに uv がインストールされていることを確認してください。
クライアントで設定します:
サーバーはデフォルトでhttps://en.wikipedia.org/ を使用します。また、他のWikiサイトを検索するように設定することもできます。
Wiki サイトがこのサーバーで動作するかどうかを確認するには、MediaWiki ソフトウェアを使用しているかどうかを確認します (通常、サイトの下部にアイコンで表示されます)。
さらに詳しく確認し、エンドポイント（通常はウェブサイトのドメイン、例えばhttps://mediawiki.org/ ）を見つけるには、ブラウザで base-url/rest.php/v1/page （例えばhttps://noita.wiki.gg/rest.php/v1/page ）にアクセスし、出力が正しいかどうかを確認してください。正しくない場合は、ベースURLに「/w」を追加してもう一度お試しください。
次に、このエンドポイントを --base-url として設定します。
{
"mcpServers": {
"mediawiki-mcp-server": {
"command": "uvx",
"args": [
"mediawiki-mcp-server",
"--base-url", "https://example.com/"
],
"env": {
"HTTP_PROXY": "http://example.com:port"
}
}
}
}または、このサーバーをソースから実行する場合:
{
"mcpServers": {
"mediawiki-mcp-server": {
"command": "uv",
"args": [
"run",
"--directory",
"mediawiki-mcp-server",
"path/to/project/src/mediawiki_mcp_server",
"--base-url", "https://example.com/"
],
"env": {
"HTTP_PROXY": "http://example.com:port"
}
}
}
}query : 検索語（短くて焦点を絞ったものが望ましい）
limit : 返される結果の最大数（デフォルト: 5）
title : 取得するWikipediaページの正確なタイトル
npx @modelcontextprotocol/inspector uv run mediawiki-mcp-server役に立つかもしれないドキュメントをいくつか紹介します。
このサーバーは現在開発中です。貢献を歓迎します！問題やプルリクエストをお気軽にご提出ください。
Cherry Studio : 複数の LLM プロバイダーをサポートするデスクトップ クライアント。MCP がサポートされています。
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
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool does (retrieves page content) but lacks critical behavioral details such as authentication requirements, rate limits, error handling, or whether it's a read-only operation (though implied by 'Get'). This leaves significant gaps for an agent to understand operational constraints.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is efficiently structured with a clear purpose statement followed by labeled sections for Args and Returns. Every sentence adds value without redundancy, making it easy to parse and understand quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read operation with one parameter and no output schema, the description covers the basics (purpose, parameter hint, return type). However, without annotations or output schema, it lacks details on response format (e.g., structured data vs. raw text), error cases, or prerequisites, leaving some contextual gaps for reliable agent use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description adds meaningful context for the single parameter 'title' by explaining that it 'can be found in title field of the search results,' which clarifies its source and usage. Since schema description coverage is 0% and there's only one parameter, this compensates well, though it doesn't detail format constraints like case sensitivity or special characters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Get a page') and resource ('from mediawiki.org'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from the sibling 'search' tool, which appears to be a related but distinct operation for finding pages rather than retrieving specific content.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives like the 'search' sibling. It mentions that titles 'can be found in title field of the search results,' which hints at a workflow but doesn't explicitly state when to choose get_page over search or other potential tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | ||
| limit | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the search returns a list of pages, which is helpful. However, it doesn't address important behavioral aspects like pagination, sorting, relevance ranking, error conditions, or performance characteristics. For a search tool with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is appropriately concise with three clear sections: purpose statement, usage advice, parameter documentation, and return value. Each sentence serves a distinct purpose. The structure with labeled 'Args:' and 'Returns:' sections is helpful, though the formatting could be cleaner.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a search tool with 2 parameters, no annotations, and no output schema, the description provides basic but incomplete coverage. It explains what the tool does and documents parameters, but lacks details about the search algorithm, result format beyond 'list of pages,' error handling, or performance considerations. The absence of output schema means the description should ideally explain the return structure more thoroughly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the schema provides no parameter documentation. The description explicitly documents both parameters: 'query: The query to search for' and 'limit: The number of results to return.' This adds meaningful semantics beyond the bare schema. However, it doesn't provide format guidance for the query or explain the default limit value (5 from schema).
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: 'Search for a wiki page.' It specifies the resource (wiki page) and action (search). However, it doesn't explicitly differentiate from the sibling tool 'get_page' - we can infer search returns multiple results while get_page likely retrieves a specific page, but this distinction isn't stated.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides some usage guidance: 'The shorter the request, the better, preferably containing only the main term to be searched.' This offers practical advice but doesn't explicitly state when to use this tool versus the 'get_page' sibling. There's implied context that this is for finding pages rather than retrieving specific ones, but no explicit alternative guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
get_pagesearchScored 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.
An MCP server that gives your AI access to the source code and docs of all public github repos
Driflyte MCP server which lets AI assistants query topic-specific knowledge from web and GitHub.
MCP server for AI dialogue using various LLM models via AceDataCloud
