Skip to main content
Glama
jam-nodes-docs-mcp

jam-nodes-docs-mcp

by KNQuoc

jam-nodes-docs-mcp

MCP (Model Context Protocol) server that exposes jam-nodes documentation as tools, so AI agents can query docs contextually without loading everything into context.

Tools

Tool

Description

search_docs

Keyword search across all documentation

get_node_info

Full docs for a specific node by type (e.g. http_request)

list_nodes

List all 16 built-in nodes with descriptions

get_api_reference

API docs for core types, registry, execution context, editor

get_guide

Get the creating-nodes guide or quick start

Related MCP server: okfy

Installation

npm install -g jam-nodes-docs-mcp

Or run directly:

npx jam-nodes-docs-mcp

Configuration

Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "jam-nodes-docs": {
      "command": "npx",
      "args": ["jam-nodes-docs-mcp"]
    }
  }
}

Cursor

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "jam-nodes-docs": {
      "command": "npx",
      "args": ["jam-nodes-docs-mcp"]
    }
  }
}

OpenClaw

Add to your MCP config:

{
  "jam-nodes-docs": {
    "command": "npx",
    "args": ["jam-nodes-docs-mcp"]
  }
}

Development

npm install
npm run build
npm start

License

MIT © KNQuoc

Available Tools

5 tools
get_api_referenceA

Get jam-nodes API reference for a specific area. Areas: "core", "types", "registry", "execution-context", "editor", "workflow-runner", "schema-introspector", "nodes".

Inputs: area (required).

get_guideB

Get a jam-nodes guide. Available guides: "creating-nodes" (custom node guide), "quick-start" (overview), "editor" (visual editor).

Inputs: guide (required).

get_node_infoA

Get full documentation for a specific built-in jam-nodes node by its type identifier (e.g. "http_request", "conditional", "filter").

Inputs: type (required).

list_nodesA

List all 16 built-in jam-nodes nodes with their type, name, category, and brief description.

Inputs: no named parameters.

search_docsA

Search jam-nodes documentation by keywords. Returns relevant sections from all docs (core API, nodes, editor, guides).

Inputs: query (required), maxResults.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct documentation resource: keyword search, individual node details, node listing, API reference, and guides. There is no meaningful overlap in their primary functions.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (search_docs, get_node_info, list_nodes, get_api_reference, get_guide). The naming is predictable and uniform.

    Tool Count5/5

    With 5 tools, the server is well-scoped for a documentation-focused MCP. Each tool covers a clear aspect of accessing documentation without unnecessary redundancy or bloat.

    Completeness5/5

    The tool set covers all major ways users interact with docs: searching, listing available nodes, retrieving node details, accessing API reference, and reading guides. No obvious dead ends or missing operations for the documented scope.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers