npm @llmgraph/mcp-serverstdioMITupdated 1mo ago
A Model Context Protocol (MCP) server that exposes your LLMGraph workflow deployments as MCP tools. Connect it to Claude Desktop, Claude Code, Cursor, or any other MCP client, and your assistant can invoke the workflows you built and deployed on LLMGraph.
llmgraph で何ができる?
@llmgraph/mcp-server
A Model Context Protocol (MCP) server that exposes your LLMGraph workflow deployments as MCP tools. Connect it to Claude Desktop, Claude Code, Cursor, or any other MCP client, and your assistant can invoke the workflows you built and deployed on LLMGraph.
Each configured deployment becomes one MCP tool. The server runs over stdio and is designed to be launched with npx, so there is nothing to install permanently.
Prerequisites
- Node.js 18 or newer
- A deployed LLMGraph workflow: copy the deployment endpoint URL (shaped like
https://llmgraph.ai/api/<graph_id>/<environment>) and an API key from the LLMGraph dashboard
Configuration
All configuration is via environment variables.
Single deployment (simple path)
| Variable | Required | Description |
|---|---|---|
LLMGRAPH_ENDPOINT |
yes | Full deployment endpoint URL copied from the dashboard |
LLMGRAPH_API_KEY |
yes | Secret API key for the deployment |
LLMGRAPH_TOOL_NAME |
no | Tool name shown to the client (default: invoke_workflow) |
LLMGRAPH_TOOL_DESCRIPTION |
no | Tool description shown to the model |
LLMGRAPH_SCHEMA_MODE |
no | input (default) or chat, see below |
LLMGRAPH_TIMEOUT_MS |
no | Request timeout in milliseconds, positive integer (default: 180000). Applies in both single and multiple deployment modes. |
Multiple deployments (advanced path)
Set LLMGRAPH_DEPLOYMENTS to a JSON array; each entry becomes one tool. When set, it takes precedence over the single-deployment variables.
[
{
"name": "summarize_document",
"description": "Summarizes a document with the LLMGraph summarizer workflow",
"endpoint": "https://llmgraph.ai/api/abc123/production",
"apiKey": "your-api-key"
},
{
"name": "support_bot",
"description": "Asks the support assistant workflow a question",
"endpoint": "https://llmgraph.ai/api/def456/production",
"apiKey": "your-other-api-key",
"inputSchema": "chat"
}
]
Schema modes
input(default): the tool takes{ "input": <object> }and the object is passed through unchanged as the POST body, so it works with any workflow input shape.chat: for chat-style workflows. The tool takes{ "user_input": <string>, "history": [{"role": "user"|"assistant", "content": <string>}] }(history optional) and sends it in the shape chat workflows expect.
Client setup
Claude Desktop
Add to claude_desktop_config.json (Settings, Developer, Edit Config):
{
"mcpServers": {
"llmgraph": {
"command": "npx",
"args": ["-y", "@llmgraph/mcp-server"],
"env": {
"LLMGRAPH_ENDPOINT": "https://llmgraph.ai/api/abc123/production",
"LLMGRAPH_API_KEY": "your-api-key",
"LLMGRAPH_TOOL_NAME": "summarize_document",
"LLMGRAPH_TOOL_DESCRIPTION": "Summarizes a document with my LLMGraph workflow"
}
}
}
}
Restart Claude Desktop and the tool appears in the tools menu.
Claude Code
claude mcp add llmgraph \
--env LLMGRAPH_ENDPOINT=https://llmgraph.ai/api/abc123/production \
--env LLMGRAPH_API_KEY=your-api-key \
-- npx -y @llmgraph/mcp-server
Cursor
Add to ~/.cursor/mcp.json (or .cursor/mcp.json in your project):
{
"mcpServers": {
"llmgraph": {
"command": "npx",
"args": ["-y", "@llmgraph/mcp-server"],
"env": {
"LLMGRAPH_ENDPOINT": "https://llmgraph.ai/api/abc123/production",
"LLMGRAPH_API_KEY": "your-api-key"
}
}
}
}
Error handling
Non-200 responses from the LLMGraph API are returned to the client as MCP tool errors carrying the API's error message:
| Status | Meaning |
|---|---|
| 400 | invalid request body |
| 401 | missing or invalid API key |
| 402 | subscription blocked |
| 403 | API disabled or origin not allowed |
| 404 | unknown deployment or wrong API key |
| 422 | workflow run failed |
| 429 | rate or budget limited |
| 504 | workflow timed out |
Security notes
- LLMGraph API keys are secrets for server-side use. This server sends the key only as the
x-api-keyheader of requests to your configured endpoint, and never writes it to stdout, stderr, or error messages. - Client config files like
claude_desktop_config.jsonstore the key in plain text on your machine; treat them accordingly.
Development
npm install
npm run build # compiles TypeScript to dist/
npm test # builds, then runs unit tests (node --test), no network calls
License
MIT, see LICENSE.
インストール
llmgraph をクライアントに追加します。お使いのものを選んでください。
claude mcp add mcp-server -- npx -y @llmgraph/mcp-servercodex mcp add mcp-server -- npx -y @llmgraph/mcp-serveramp mcp add mcp-server -- npx -y @llmgraph/mcp-server{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@llmgraph/mcp-server"
]
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@llmgraph/mcp-server"
]
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
code --add-mcp '{"name":"mcp-server","command":"npx","args":["-y","@llmgraph/mcp-server"]}'Or add the block manually to `.vscode/mcp.json` under `servers`.
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@llmgraph/mcp-server"
]
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@llmgraph/mcp-server"
]
}
}
}Add to `cline_mcp_settings.json` via the MCP Servers panel.
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@llmgraph/mcp-server"
]
}
}
}Add to `~/.gemini/settings.json`.
{
"mcpServers": {
"mcp-server": {
"type": "local",
"command": "npx",
"args": [
"-y",
"@llmgraph/mcp-server"
],
"tools": [
"*"
]
}
}
}Add to `~/.copilot/mcp-config.json`, or run `/mcp add` inside the CLI.
{
"context_servers": {
"mcp-server": {
"command": {
"path": "npx",
"args": [
"-y",
"@llmgraph/mcp-server"
]
}
}
}
}Add to your Zed `settings.json`.
npx -y @llmgraph/mcp-serverRun `goose configure`, choose **Add Extension → Command-line Extension**, and paste this command.
スコア
39 / 100
情報不足
- ドキュメント25/25
- メンテナンス16/25
- 信頼性13/20
- 機能0/15
- 導入のしやすさ12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 48 days ago
- Has a release history
- Repository is not archived
- Licensed MIT
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 0 tool(s) documented
- Provides prompt templates
- Provides resources
- 12 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint — no local install
バージョン履歴
| バージョン | 公開日 |
|---|---|
| 0.1.1最新 | 2026年7月15日 |