@llmgraph/mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LLMGRAPH_API_KEY | No | Secret API key for the deployment | |
| LLMGRAPH_ENDPOINT | No | Full deployment endpoint URL copied from the dashboard | |
| LLMGRAPH_TOOL_NAME | No | Tool name shown to the client | invoke_workflow |
| LLMGRAPH_TIMEOUT_MS | No | Request timeout in milliseconds | 180000 |
| LLMGRAPH_DEPLOYMENTS | No | JSON array of deployment configurations for multiple deployments | |
| LLMGRAPH_SCHEMA_MODE | No | Schema mode: input or chat | input |
| LLMGRAPH_TOOL_DESCRIPTION | No | Tool description shown to the model |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| productionB | Invoke the LLMGraph workflow deployment "production" |
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 1 tool
With only one tool, there is no possibility of confusing it with another. The tool name is unique within the server, so an agent can unambiguously select it.
The single tool name 'production' is a noun rather than an action-oriented verb_noun pattern, and there are no other tools to establish a consistent convention. The name is vague and does not clearly indicate what operation it performs.
A single tool named 'production' that only invokes a workflow deployment is extremely thin for a server, appearing more like a one-off action than a coherent toolset. This falls at the extreme low end of the count appropriateness scale.
The server exposes no other lifecycle operations around deployments—there is no way to list, create, update, or delete workflows, or to invoke any environment other than 'production'. This is a severely incomplete surface for any real workflow management purpose.