Developer · Local MCP server
Llmgraph
Invoke deployed LLMGraph no-code LLM workflows (chat, RAG, automations) as MCP tools.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.abahocodes/llmgraph- Version
- 0.1.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-07-15
- Updated
- 2026-07-15
- Publisher
- abahocodes (GitHub)
- Website
- llmgraph.ai
- Repository
- github.com/abahocodes/llmgraph-mcp-server
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @llmgraph/mcp-server | 0.1.1 | stdio |
How to connect Llmgraph
Llmgraph runs locally from a Node.js package published to the npm registry: @llmgraph/mcp-server version 0.1.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y @llmgraph/mcp-server@0.1.1. It reads these environment variables: LLMGRAPH_ENDPOINT (required) and LLMGRAPH_API_KEY (required, secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"llmgraph": {
"command": "npx",
"args": [
"-y",
"@llmgraph/mcp-server@0.1.1"
],
"env": {
"LLMGRAPH_ENDPOINT": "<value>",
"LLMGRAPH_API_KEY": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| LLM SEO MCP — Elephant AccountabilityLLM SEO and Agent Discoverability for B2B SaaS. Pricing, fit assessment, audit requests. | Remote · HTTP |
| LLM UsageLocal-first, multi-provider tool that captures LLM API spend and exposes it to coding agents via MCP. | Local · stdio |
| Llm Wiki MCPMCP server for Karpathy-style LLM wikis: persistent markdown your agent grows over time. | Local · stdio |
| llm-oracleUp-to-date LLM pricing + availability catalog with cited sources for AI agent routing. | Local · stdio |
| LlmrefVersioned documentation registry and semantic search for AI tools and coding assistants. | Remote · HTTP |
| Llmtest MCPBenchmark AI models on real prompts. Find cheaper, faster alternatives across 340+ models. | Local · stdio |
| llmtrimMCP server and proxy that compresses LLM prompts, tool output, and replies to cut token cost. | Local · stdio |
| LmConnect Claude to any OpenAI-compatible LLM endpoint and offload routine work to a local model. | Local · stdio |