How do I use Minecraft Wiki MCP Server?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Minecraft Wiki MCP Server search wiki for 'redstone mechanics'" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

Minecraft Wiki MCP Server

by rice-awa

Overview Schema Source Related Servers Discussions Admin

Python

Remote

Minecraft Wiki MCP Server

English

Project Overview

A MCP-based Minecraft Wiki server that provides convenient access to Chinese Minecraft Wiki content. Supports stdio, SSE and http transports in a single package, and can be deployed quickly via uvx.

Note: This project only provides the MCP layer on top of a Minecraft wiki API. For local API deployment, please visit minecraft-wiki-fetch-api.

Features

🔍 Wiki Search: Search Chinese Minecraft Wiki pages with concise keyword guidance
📄 Page Retrieval: Get full page content in wikitext (default, token-efficient) or html
✅ Page Existence Check: Quick check if a page exists (including redirects)
📚 Namespace Listing: List available wiki namespaces for targeted search
🏥 Health Monitoring: Monitor backend Wiki API service status
🔌 Multi Transport: stdio (Claude Desktop / local clients), http (remote/server), sse (legacy)
🚀 One-Click Deployment: Run via uvx without local install
⚙️ Env + CLI Config: Flexible configuration via environment variables and CLI flags

Related MCP server: mcp-mediawiki-crunchtools

Quick Start

🚀 Recommended: Using uvx

# stdio (default) — for Claude Desktop / local MCP clients
uvx mc-wiki-fetch-mcp

# http — for remote / server deployment
uvx mc-wiki-fetch-mcp --transport http --host 0.0.0.0 --port 3001

# Custom Wiki API URL
uvx mc-wiki-fetch-mcp --api-url http://localhost:3000

# Or via environment variables
MC_WIKI_API_BASE_URL=http://localhost:3000 \
MC_WIKI_MCP_TRANSPORT=http \
uvx mc-wiki-fetch-mcp

# Help
uvx mc-wiki-fetch-mcp --help

💻 Integration with Claude Desktop (stdio)

Config file locations:
- Windows: %APPDATA%\Claude\claude_desktop_config.json
- macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
- Linux: ~/.config/claude/claude_desktop_config.json

Edit configuration:

{
  "mcpServers": {
    "minecraft-wiki": {
      "command": "uvx",
      "args": ["mc-wiki-fetch-mcp"],
      "env": {
        "MC_WIKI_API_BASE_URL": "https://mcwiki.rice-awa.top"
      }
    }
  }
}

Restart Claude Desktop

🌐 Remote / HTTP clients (http)

uvx mc-wiki-fetch-mcp -t http --host 0.0.0.0 --port 3001

Point your MCP client to the Streamable HTTP endpoint (must include /mcp):

http://<host>:3001/mcp

Example client config:

{
  "mcpServers": {
    "minecraft-wiki": {
      "url": "http://127.0.0.1:3001/mcp"
    }
  }
}

Note: The endpoint is /mcp, not the root /. Connecting to http://host:3001 will cause list_tools / tools/list to return 404. Use transport type http / streamable-http, not SSE.

Configuration Options

Environment Variables

Environment Variable	Description	Default
`MC_WIKI_API_BASE_URL` / `API_BASE_URL`	Wiki API base URL	`https://mcwiki.rice-awa.top`
`MC_WIKI_API_TIMEOUT`	API request timeout (seconds)	`60`
`MC_WIKI_MCP_TRANSPORT`	Transport: `stdio` / `sse` / `http`	`stdio`
`MC_WIKI_MCP_HOST`	Bind host (HTTP/SSE)	`0.0.0.0`
`MC_WIKI_MCP_PORT`	Bind port (HTTP/SSE)	`3001`
`MC_WIKI_MCP_NAME`	MCP server display name	`Minecraft Wiki`
`MC_WIKI_LOG_LEVEL`	Log level	`INFO`

Command Line Arguments

Parameter	Description
`--transport`, `-t`	`stdio` / `sse` / `http`
`--host`	Bind host for HTTP/SSE
`--port`, `-p`	Bind port for HTTP/SSE
`--api-url`	Wiki API base URL
`--timeout`	API request timeout (seconds)
`--log-level`	`DEBUG` / `INFO` / `WARNING` / `ERROR` / `CRITICAL`
`--name`	MCP server display name
`--version`	Show version
`--help`	Show help

Priority: CLI args > environment variables > defaults.

Available Tools

Tool	Description	Main Parameters
`search_wiki`	Search Chinese Minecraft Wiki	`q`, `limit`, `namespaces`
`get_page`	Get page content (wikitext/html)	`pageName`, `format`, `useCache`, `includeMetadata`
`check_page_exists`	Check whether a page exists	`pageName`
`check_health`	Check Wiki API health	—
`list_namespaces`	List wiki namespace ID → name map	—

Tips for Agents

Prefer 1–3 game terms in search_wiki; extra keywords narrow results.
Prefer wikitext for get_page (default). Use html only when a template is unreadable.
Unknown {{Template}} in wikitext → call search_wiki with namespaces=[10].

Traditional Installation (Developers)

git clone <repository-url>
cd mc-wiki-mcp-pypi

pip install -e .
# or: uv pip install -e .

# stdio
mc-wiki-fetch-mcp

# http
mc-wiki-fetch-mcp -t http -p 3001

Troubleshooting

uvx not found

curl -LsSf https://astral.sh/uv/install.sh | sh
# or
pip install uv

Cannot connect to Wiki API

echo $MC_WIKI_API_BASE_URL
curl http://your-api-url/health
MC_WIKI_LOG_LEVEL=DEBUG uvx mc-wiki-fetch-mcp

Tools not visible in Claude Desktop

Confirm uvx mc-wiki-fetch-mcp --version works
Check Claude Desktop logs
Restart Claude Desktop

HTTP client returns 404 on list_tools

Confirm the client URL is http://<host>:<port>/mcp (the trailing /mcp is required)
Use transport http / streamable-http, not SSE
After restarting the server, reconnect the client so it gets a fresh session

API Documentation — Detailed API interface documentation
Modification Summary — Recent packaging changes

Contributing

Issues and Pull Requests are welcome!

License

MIT License — see LICENSE.

Getting Help

Check the troubleshooting section above
Browse docs/
Open an Issue with logs

Quick tips

🚀 Local client: uvx mc-wiki-fetch-mcp (stdio)
🌐 Server mode: uvx mc-wiki-fetch-mcp -t http -p 3001
⚙️ Configure: env vars or CLI flags
🔧 Develop: pip install -e .

Available Tools

5 tools

check_healthA

检查 Wiki API 服务健康状态。

ParametersJSON Schema

Name	Required	Description	Default
No parameters

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A3.6/5.0

Behavior2/5

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

No annotations provided, and the description does not disclose any behavioral traits beyond checking health. It does not mention side effects, rate limits, or response structure, which is minimal for a health check tool.

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 a single sentence that directly states the purpose. It is concise, front-loaded, and contains no extraneous 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 is a simple health check with no parameters and an output schema exists, the description is mostly complete. However, it could briefly indicate what the response indicates (e.g., healthy/unhealthy), but the output schema likely covers this.

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?

No parameters exist, so the description does not need to add parameter meaning. Baseline score for 0 parameters is 4 according to guidelines.

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 checks the health status of the Wiki API service, with a specific verb and resource. It distinguishes from sibling tools which deal with pages, search, and namespaces.

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

Usage Guidelines2/5

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

No guidance on when to use this tool or alternatives. The description only states what it does, not when it should be invoked or any prerequisites.

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

check_page_existsC

检查页面是否存在。

ParametersJSON Schema

Name	Required	Description	Default
`pageName`	Yes	页面名称，支持中文

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It states the tool checks existence, implying a read-only operation, but does not mention permissions, side effects, or error handling.

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 an efficient single sentence. It is appropriately concise for a simple tool, though it could include a brief usage hint without becoming verbose.

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

Completeness3/5

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

Given the tool's simplicity (one parameter, boolean return likely), the description is minimally complete. However, it lacks details on output format or error states, especially with no annotations to supplement.

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 schema has 100% coverage as the only parameter 'pageName' has a description ('支持中文'). The tool description adds no additional meaning beyond the schema, so baseline score is appropriate.

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

Purpose4/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: checking if a page exists. It uses a specific verb and resource, but does not differentiate from siblings like 'get_page' which might also imply existence checking.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'get_page' or 'search_wiki'. The description lacks any contextual hints for appropriate usage.

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

get_pageA

获取 Minecraft 中文 Wiki 页面的内容。

根据页面名称获取 Wiki 页面的完整内容。

格式选择：

wikitext（默认）：Wiki 原始标记语言，{{Template}} 完整保留，信息最全。
html：清洗后的正文 HTML。仅当 wikitext 中某个模板语法确实无法理解时才使用。

wikitext 中遇到不认识的 {{Template}} 时，可用 search_wiki 传 namespaces=[10] 去模板命名空间搜索该模板的文档。

ParametersJSON Schema

Name	Required	Description	Default
`format`	No	非必要不要传此参数，默认 wikitext 就是最好的。 wikitext 完全保留模板语义；html 仅在 wikitext 模板确实无法理解时使用	wikitext
`pageName`	Yes	页面名称，支持中文。例如 '钻石'、'工作台'、'命令'
`useCache`	No	是否使用缓存，默认 true
`includeMetadata`	No	是否包含元数据，默认 true

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A4.6/5.0

Behavior4/5

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

No annotations provided, so description carries full burden. It explains format selection and cache behavior (via useCache in schema), but does not mention potential errors, permissions, or output structure. Output schema exists, so return format is covered.

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?

Description is well-structured: starts with purpose, then format details and alternative tool. Every sentence adds value; no redundancy.

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 4 parameters (1 required) and an output schema, description covers core functionality well. However, does not mention useCache or includeMetadata parameters (though schema covers them) and could briefly note caching behavior. Overall complete for content retrieval.

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 description adds value by reinforcing format guidance ('非必要不要传此参数') and explaining wikitext vs html. For pageName, it confirms Chinese language support, consistent with schema.

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?

Description clearly states verb '获取' and resource 'Minecraft 中文 Wiki 页面的内容', specifying exactly what the tool retrieves. It distinguishes from sibling tools like check_page_exists (existence check) and search_wiki (searching).

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

Usage Guidelines5/5

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

Explicitly guides when to use wikitext vs html format, and advises using search_wiki for template documentation. Provides clear context for tool selection.

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

list_namespacesA

获取 Minecraft Wiki 的命名空间映射表。

返回所有可用命名空间的数字 ID 和对应名称。结合 search_wiki 的 namespaces 参数使用。

ParametersJSON Schema

Name	Required	Description	Default
No parameters

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A4.2/5.0

Behavior3/5

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

No annotations provided, so the description must disclose behavior. It describes the return value but does not mention read-only nature, authentication needs, or rate limits. For a simple retrieval tool, this is adequate but not comprehensive.

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 consists of two concise sentences with no waste. The first sentence states the purpose, and the second provides usage context, making it well-structured and front-loaded.

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 output schema exists, explanation of return values is unnecessary. The description sufficiently covers purpose and integration with search_wiki. Minor missing details about assumed multi-wiki context, but acceptable for this simple tool.

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?

No parameters exist in the schema (0 params), so description need not add param details. Baseline 4 applies as per guidelines.

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?

Description clearly states the tool retrieves the namespace mapping table for Minecraft Wiki, returning numeric IDs and names. It distinguishes from sibling tools (e.g., search_wiki, get_page) by its specific function.

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

Usage Guidelines4/5

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

Explicitly advises to use this tool in conjunction with search_wiki's namespaces parameter, providing clear context for when to invoke it. No explicit exclusions, but the guidance is useful.

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

search_wikiA

搜索 Minecraft 中文 Wiki。

用1-3个游戏名词查找匹配的页面。多关键词会缩小范围（所有词须同时出现在结果页面中），如需多角度搜索应分批调用本工具，而非把大量关键词堆在一次查询中。

ParametersJSON Schema

Name	Required	Description
`q`	Yes	搜索关键词，1-3个游戏名词为佳。多关键词会缩小而非扩大范围，因为所有词都需出现在结果页面中。如需多角度搜索，分别调用本工具即可。这不是搜索引擎，不要堆砌关键词。例：'信标激活'，而不是 '信标激活怎么做教程步骤'
`limit`	No	返回结果数量，默认 10，最大 50
`namespaces`	No	限定命名空间，数字ID列表。0=Main 10=Template 14=Category 9994=Module。空则使用默认值

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A4.3/5.0

Behavior4/5

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

Without annotations, the description carries the full burden. It explains that multiple keywords narrow results and that the tool is not a general search engine. This helps manage expectations. The existence of an output schema further aids transparency, though more details on pagination or errors could be beneficial.

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 concise with two short paragraphs. The first sentence immediately states the purpose, and the rest provides actionable tips. No unnecessary words. Could be slightly more structured, but it is efficient.

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 (3 parameters, output schema present), the description covers the core functionality and usage patterns. It addresses keyword selection and batching. Missing details like error handling or rate limits are acceptable for a search tool with an output schema.

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% (all params have descriptions), so baseline is 3. The description adds significant value beyond the schema: for 'q', it provides examples ('信标激活') and clarifies that multiple keywords narrow instead of broaden. This improves usability.

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: '搜索 Minecraft 中文 Wiki' (search the Chinese Minecraft Wiki). It uses a specific verb and resource, and the sibling tools (check_page_exists, get_page) indicate that this tool is for searching, not for direct page retrieval or existence checks.

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

Usage Guidelines4/5

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

The description provides clear usage guidelines: use 1-3 keywords, multiple keywords narrow the range (all must appear), and for multi-angle searches, batch calls instead of piling keywords. While it does not explicitly mention when not to use it or compare to siblings, the context from sibling names implies it is for search, not other operations.

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.

5 tool updatesv0.5.0Jul 29, 2026
- First observedcheck_health
- First observedcheck_page_exists
- First observedget_page
- First observedlist_namespaces
- First observedsearch_wiki

Deploy Server

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

TDQS

A3.9/5.0

Scored 2026-07-29 06:30 across 5 tools

Disambiguation5/5

Each tool has a distinct purpose: checking existence, searching, fetching page content, health check, and listing namespaces. No overlap in functionality.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., check_page_exists, search_wiki, get_page). No inconsistencies.

Tool Count5/5

With 5 tools, the server is well-scoped for read-only wiki operations: existence check, search, content retrieval, health, and namespace mapping. Appropriate for the domain.

Completeness4/5

Covers core read operations (search, get, check existence) and auxiliary (health, namespaces). Missing list_pages or revision retrieval, but not critical for basic wiki access.

Maintenance

ActivitySlowing

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Related MCP Connectors

EcoCarbonWiki A
dev.carbonitex.ecogame
Read-only MCP for the Eco game wiki: search, Markdown pages, and wiki_* lookups. No keys, no writes.
Documentation Access Search Games & Gamification
101
FlowdexOAuth
dk.flowdex
Read and write your team's shared, AI-readable wiki from any MCP client.
Note Taking Documentation Access Workplace & Productivity
1
Razi Web Tools A
io.github.razikallayi
Web and URL utilities over MCP: shorten URLs, screenshot pages, read page metadata, encode URLs.
Browser Automation Web Scraping
61
wikipedia A
io.github.pipeworx-io
Wikipedia MCP — wraps Wikipedia REST API (free, no auth)
Search Open Data Art & Culture
363

Related MCP Servers

mediawiki-mcp-server
Search Documentation Access Open Data
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!
Updated a year ago (2025-07-13 01:40 UTC)
2
26
-
mcp-mediawiki-crunchtools
Content Management Systems Search Developer Tools
crunchtools
A
license
B
quality
B
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.
Updated 7 days ago (2026-09-06 02:35 UTC)
19
AGPL 3.0
mediawiki-mcp-server
Content Management Systems Search Developer Tools
olgasafonova
A
license
A
quality
A
maintenance
MCP server for MediaWiki wikis. Search, read, edit, and manage wiki content from AI assistants. Includes formatting, link checking, revision history, and markdown conversion.
Updated 5 days ago (2026-09-08 12:21 UTC)
43
20
MIT
WikiJS MCP Server
Content Management Systems Knowledge & Memory Search
vnikhilbuddhavarapu
A
license
Not graded
quality
D
maintenance
An MCP server that enables full management of WikiJS instances, supporting operations like page creation, searching, and updating. It also provides tools for knowledge graph exploration, content summarization, and retrieval of wiki statistics.
Updated 6 months ago (2026-03-23 15:23 UTC)
8
MIT

Minecraft Wiki MCP Server

Project Overview

Features

Quick Start

🚀 Recommended: Using uvx

💻 Integration with Claude Desktop (stdio)

🌐 Remote / HTTP clients (http)

Configuration Options

Environment Variables

Command Line Arguments

Available Tools

Tips for Agents

Traditional Installation (Developers)

Troubleshooting

uvx not found

Cannot connect to Wiki API

Tools not visible in Claude Desktop

HTTP client returns 404 on list_tools

Related Documentation

Contributing

License

Getting Help

Available Tools

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers