jam-nodes-docs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_docsA | Search jam-nodes documentation by keywords. Returns relevant sections from all docs (core API, nodes, editor, guides). |
| get_node_infoA | Get full documentation for a specific built-in jam-nodes node by its type identifier (e.g. "http_request", "conditional", "filter"). |
| list_nodesA | List all 16 built-in jam-nodes nodes with their type, name, category, and brief description. |
| get_api_referenceA | Get jam-nodes API reference for a specific area. Areas: "core", "types", "registry", "execution-context", "editor", "workflow-runner", "schema-introspector", "nodes". |
| get_guideB | Get a jam-nodes guide. Available guides: "creating-nodes" (custom node guide), "quick-start" (overview), "editor" (visual editor). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
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.
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.
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.
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.