Skip to main content
Glama
HytaleModding.dev MCP Server

HytaleModding.dev MCP Server

by jmrapp1

HytaleModding.dev MCP Server

An MCP (Model Context Protocol) server that provides AI tools with access to the HytaleModding.dev documentation. Run it locally and connect it to Claude Desktop, Cursor, Windsurf, or any MCP-compatible client.

Watch how Claude uses it to built out a user interface: HytaleModding MCP Server Demo

Tools

search_docs

Search the documentation index. Returns matching pages and sections grouped by page with URLs and breadcrumb paths.

Parameter

Type

Required

Default

Description

query

string

yes

Search query text

locale

string

no

"en"

Locale code

limit

number

no

10

Limits the number of pages returned

get_doc

Fetch the full content of a documentation page, converted from HTML to readable text.

Parameter

Type

Required

Description

path

string

yes

Page path, e.g. /en/docs/official-documentation/custom-ui/markup

Related MCP server: Roblox Documentation MCP Server

Prerequisites

  • Node.js 18+

  • npm

Setup

npm install
npm run build

Running the server

The MCP-server communicates over stdio (stdin/stdout) using JSON-RPC, which is how MCP clients launch and talk to it, so there's no need to have an ever-running server. AI clients will trigger the requests directly against the dist/index.js file (refer to the testing manually section).

Client configuration

Claude Desktop

Add to your claude_desktop_config.json:

a

Cursor

Go to Cursor Settings > Tools & Integrations > MCP Tools and add:

{
  "mcpServers": {
    "hytalemodding-docs": {
      "command": "node",
      "args": ["/absolute/path/to/hytalemodding-mcp-server/dist/index.js"]
    }
  }
}

Windsurf

Open Command Palette > Windsurf MCP Configuration Panel and add the same JSON block as above.

Claude Code

Run this from any directory:

claude mcp add hytalemodding-docs node /absolute/path/to/hytalemodding-mcp-server/dist/index.js

Development

Watch mode recompiles on file changes:

npm run dev

Testing manually

You can pipe JSON-RPC messages to the server over stdio to test:

# Initialize and list tools
printf '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"1.0.0"}}}\n{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}\n' | node dist/index.js 2>/dev/null

# Search for documentation
printf '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"1.0.0"}}}\n{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"search_docs","arguments":{"query":"NPC template"}}}\n' | node dist/index.js 2>/dev/null

# Fetch a specific doc page
printf '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"1.0.0"}}}\n{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"get_doc","arguments":{"path":"/en/docs/quick-start"}}}\n' | node dist/index.js 2>/dev/null

Available Tools

2 tools
get_docA

Fetch the full content of a Hytale modding documentation page. You MUST use the search_docs tool first to get a list of URLs that are compatible with this tool.

Inputs: url (required).

search_docsD

Fetch the full content of a Hytale modding documentation page. Provide a doc path (e.g. '/en/docs/official-documentation'). Use search_docs first to find the right page path.

Inputs: query (required), limit, locale. Returns: results

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.5/5.0

    Scored across 2 tools

    Disambiguation2/5

    Both tools are described as 'Fetch the full content of a Hytale modding documentation page', making them appear to do the same thing. While one is named 'search' and the other 'get', the descriptions do not clearly differentiate their purposes, leaving agents confused about which to use.

    Naming Consistency4/5

    Both tool names follow a verb_noun pattern (search_docs, get_doc), but one uses the plural 'docs' and the other singular 'doc', a minor inconsistency. The verbs 'search' and 'get' are distinct and reasonably clear.

    Tool Count3/5

    With only 2 tools, the server feels minimal. For a documentation server, a search and fetch pair is plausible, but the count is at the lower end of what is reasonable for a coherent toolset.

    Completeness3/5

    The server appears to cover searching and fetching documentation pages, but the unclear boundary between the tools leaves a gap in understanding how to discover pages without already knowing a path. A clearer search step or listing mechanism would make the surface more complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers