colyseus-docs-mcp
Provides AI agents with access to the Colyseus documentation, enabling searching, reading, and listing of documentation pages.
README
colyseus-docs-mcp
An MCP (Model Context Protocol) server that exposes the Colyseus multiplayer-framework documentation to AI agents such as opencode, Claude Code, Cursor, etc.
Published as an npm package. With this server wired up, an agent you're chatting with can:
- enumerate every documentation page (
list_docs) - read any page rendered as clean Markdown (
read_doc) - run a relevance-ranked full-text search (
search_docs) - subscribe to per-page resources (
colyseus://docs/{slug})
The MDX scaffolding (frontmatter, imports, <Tabs>, <Callout>, icon
components, JSX comments, ...) is stripped ahead of time so the agent only ever
sees prose + working code blocks.
Status
- Loads 114 doc pages from the bundled
docs/snapshot. - Speaks MCP over stdio (the standard local-server transport).
- Provides 3 tools, 1 resource template, and 1 ready-made prompt.
- Zero runtime deps beyond
@modelcontextprotocol/sdkandzod. - Lint + smoke-tested end-to-end.
Install
# Run once (downloads & caches the package)
npx -y colyseus-docs-mcp
# Or install globally
npm install -g colyseus-docs-mcp
colyseus-docs-mcp
The server speaks JSON-RPC over stdio, so running the binary directly just waits for MCP messages on stdin - point an MCP client at it (see below) rather than running it by hand.
From source
git clone https://github.com/VGFP/colyseus-docs-mcp.git
cd colyseus-docs-mcp
npm install
npm run build
node dist/index.js # speaks JSON-RPC over stdio
You can sanity-check the server without an MCP-aware client:
npm run smoke # node scripts/smoke-test.mjs - exercises every tool/resource
npm run lint # node scripts/lint-preprocessed.mjs - validates MDX stripping
npm test # build + lint + smoke
Pointing an MCP client at it
opencode
Add the following to your project's .opencode/opencode.json (or
~/.config/opencode/opencode.json for global use):
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"colyseus-docs-mcp": {
"type": "local",
"command": ["npx", "-y", "colyseus-docs-mcp"],
"enabled": true
}
}
}
If you installed it globally, the command can be just ["colyseus-docs-mcp"].
For a local build, use the absolute path to dist/index.js:
{
"mcp": {
"colyseus-docs-mcp": {
"type": "local",
"command": ["node", "/absolute/path/to/colyseus-docs-mcp/dist/index.js"],
"enabled": true
}
}
}
Restart opencode after saving the file - MCP servers are loaded once at startup.
Other MCP clients (Claude Code, Cursor, etc.)
The server speaks standard MCP over stdio, so any compliant client works. Use
npx -y colyseus-docs-mcp or node /path/to/dist/index.js as the launch
command.
Tools
list_docs
Returns the catalogue of every documentation page known to the server. Use this first when you don't know which page covers a topic.
// Input
{}
// Output (truncated)
{
"total": 114,
"docs_root": "/abs/path/to/colyseus-docs-mcp/docs",
"pages": [
{ "slug": "", "title": "Colyseus - Multiplayer Game Framework for Node.js", "category": "index", "description": "…" },
{ "slug": "state", "title": "State Synchronization", "category": "state", "description": null },
{ "slug": "room/messages", "title": "Message Composability", "category": "room", "description": null },
…
]
}
read_doc
Returns the preprocessed Markdown body of a single page.
// Input
{ "slug": "state" } // "" or "index" returns the landing page
// Output
{
"content": [
{ "type": "text", "text": "# State Synchronization\n\n…full Markdown…" }
]
}
The slug lookup is forgiving - "state", "/state", "state/", and
"index" are all accepted.
search_docs
Relevance-ranked full-text search. Title hits weighted highest, then headings, then body. Each hit includes a ~250-character snippet around the first match.
// Input
{ "query": "schema @type decorator", "limit": 5 }
// Output
{
"query": "schema @type decorator",
"total_hits": 3,
"hits": [
{
"slug": "state/schema",
"title": "Schema Definition",
"category": "state",
"score": 23,
"snippet": "…the **@type** decorator marks each property…"
},
…
]
}
Resources
A single URI template is registered so clients can also use resources/read
instead of tools/call if they prefer:
colyseus://docs/{slug}
Example:
{ "uri": "colyseus://docs/room" }
Prompts
| Name | Purpose |
|---|---|
colyseus_overview |
Returns a system-style primer describing Colyseus + the full doc index. |
Configuration
| Env var | Default | Purpose |
|---|---|---|
COLYSEUS_DOCS_PATH |
<package_root>/docs |
Override the docs directory. |
Pointing COLYSEUS_DOCS_PATH at a fresh clone of
https://github.com/colyseus/docs is the easiest way to pull in upstream
changes - the server reads MDX at startup, so just restart it after a git pull.
Updating the bundled docs
The docs/ directory is a snapshot of Colyseus's MDX pages. To refresh it:
# From another directory of your choice:
git clone https://github.com/colyseus/docs.git upstream-docs
# Back in this package:
rm -rf docs && cp -r ../upstream-docs/pages ./docs
npm run lint && npm run smoke
Releasing
The package version mirrors the Colyseus version whose docs are bundled, with an
-mcp.N suffix for successive MCP-only revisions against the same upstream
release (e.g. 0.17.10-mcp.1, 0.17.10-mcp.2, …). When you sync docs/ from
upstream, bump the upstream segment and reset the MCP counter:
# After `npm run lint && npm run smoke` pass with the refreshed docs:
# New upstream release → reset mcp counter:
npm version 0.18.0-mcp.1
# Same upstream, new MCP-only change → bump mcp counter:
npm version prerelease --preid mcp # 0.17.10-mcp.1 → 0.17.10-mcp.2
git push --follow-tags
Pushing a v* tag triggers .github/workflows/release.yml, which builds and
publishes to npm (with provenance). The NPM_TOKEN secret must be set in the
repository's Actions secrets.
Pre-release upstream tags (e.g.
0.18.0-preview.1) are mirrored as0.18.0-preview.1-mcp.1.
Project layout
colyseus-docs-mcp/
├── .github/workflows/
│ ├── ci.yml # build + lint + smoke on push/PR
│ └── release.yml # npm publish on version tags
├── docs/ # All MDX documentation pages (the data)
├── scripts/
│ ├── smoke-test.mjs # End-to-end JSON-RPC exercise of every tool/resource
│ └── lint-preprocessed.mjs
├── src/
│ ├── index.ts # MCP server registration + stdio transport
│ └── lib/
│ ├── docs.ts # Doc discovery + MDX → Markdown preprocessor
│ └── search.ts # Ranked full-text search
├── package.json
├── tsconfig.json
└── README.md
License
MIT (inherited from the upstream Colyseus docs - see LICENSE).
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。