Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
Invoke deployed LLMGraph no-code LLM workflows (chat, RAG, automations) as MCP tools.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
LLMGRAPH_ENDPOINT, LLMGRAPH_API_KEYValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"llmgraph": {
"command": "npx",
"args": [
"-y",
"@llmgraph/mcp-server"
],
"env": {
"LLMGRAPH_ENDPOINT": "your-value",
"LLMGRAPH_API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add llmgraph --env LLMGRAPH_ENDPOINT=your-value --env LLMGRAPH_API_KEY=your-value -- npx -y @llmgraph/mcp-serverFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"llmgraph": {
"command": "npx",
"args": [
"-y",
"@llmgraph/mcp-server"
],
"env": {
"LLMGRAPH_ENDPOINT": "your-value",
"LLMGRAPH_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"llmgraph": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@llmgraph/mcp-server"
],
"env": {
"LLMGRAPH_ENDPOINT": "your-value",
"LLMGRAPH_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account abahocodes, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: LLMGRAPH_ENDPOINT, LLMGRAPH_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Context7, Codebase Memory, Exa
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
https://llmgraph.ai/api/ / ) and an API key from the LLMGraph dashboardAll configuration is via environment variables.
| 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. |
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" } ]
input (default): the tool takes { "input": } 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": , "history": [{"role": "user"|"assistant", "content": }] } (history optional) and sends it in the shape chat workflows expect.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 mcp add llmgraph \
--env LLMGRAPH_ENDPOINT=https://llmgraph.ai/api/abc123/production \ --env LLMGRAPH_API_KEY=your-api-key \ -- npx -y @llmgraph/mcp-server
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" } } } }
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 |
x-api-key header of requests to your configured endpoint, and never writes it to stdout, stderr, or error messages.claude_desktop_config.json store the key in plain text on your machine; treat them accordingly.npm install
npm run build # compiles TypeScript to dist/ npm test # builds, then runs unit tests (node --test), no network calls
MIT, see LICENSE.