lyzr-mcp
Provides tools for managing Git repositories, including pull, branch, commit, merge, pull request, and file operations.
Provides tools for training and querying knowledge graphs backed by Neo4j, including file, website, and text training and graph retrieval.
Provides tools for creating and managing WebRTC sessions for real-time communication.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@lyzr-mcpCreate a knowledge base from our website and query it."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
lyzr-mcp
An MCP server that exposes the Lyzr Enterprise API as MCP tools, resources, and prompts.
Bring-your-own-key, like the Supabase MCP server: every user supplies their own Lyzr API key. The server authenticates as that user and never uses a shared key.
Status: runnable. All three transports (stdio, SSE, Streamable HTTP), 423 tools across the agent + rag hosts — the original core set (agents, sessions, inference, RAG/knowledge base, parse/classify, credentials, live sources, knowledge graph, Cognis memory, scheduler, RAI) plus the full remaining
agent-devOpenAPI surface (A2A, agent eval, artifacts, assets, audit logs, channels, contexts, platform admin, GitAgent, human feedback, tool requests, skills, org LLM fallbacks, reports, semantic model, sessions v3, sharing, tools v3, traces, usage alerts, widget stream, user assets, world model, agent memory providers, ops, providers, workflows) plus the full remainingrag-devOpenAPI surface (Live Sources browse/webhooks/sync-permissions, Knowledge Graph Neo4j variants, Extract, doc content, Source Auth, file-based Parse/Train for PDF/DOCX/TXT/CSV/XLSX/PPTX/image, and the full KB Sync connector subsystem including deprecated legacy endpoints) — 5 resources, and 4 prompts. Endpoints confirmed against thelyzr-adkSDK and the Lyzr OpenAPI specs.
Documentation
📖 docs/README.md — architecture, setup, env vars, transports, HTTP contract, hosting, troubleshooting.
🧰 docs/tools.md — reference for the core tools, resources, and prompts.
Related MCP server: lynxprompt-mcp
Tools (363)
See .claude/skills/lyzr-api-endpoint/SKILL.md for the conventions
used to add these, and npx lyzr-mcp-skills below for end-user-facing skills covering the core groups.
Core groups
Group | Tools |
Agents & inference |
|
Sessions & templates |
|
Knowledge Base (RAG) |
|
Parse & classify |
|
Credentials & live sources |
|
Knowledge Graph (v4) |
|
Cognis memory |
|
Scheduler |
|
RAI guardrails |
|
Extended agent-dev groups (agent host)
Group | Tools |
Agent lifecycle (extra) |
|
Inference (extra) |
|
A2A agents |
|
Agent eval |
|
Artifacts |
|
Assets |
|
Audit logs |
|
Channels |
|
Contexts |
|
Platform admin (credits/flags/modules) |
|
GitAgent |
|
Human feedback / tool requests / skills |
|
Org LLM fallbacks |
|
Reports |
|
Semantic model |
|
Sessions v3 |
|
Sharing |
|
Tools v3 (core + integrations) |
|
Traces |
|
Usage alerts / widget stream / user assets |
|
World model |
|
Agent memory providers |
|
Ops |
|
Providers (core + credentials) |
|
Workflows |
|
Extended rag-dev groups (rag host)
Group | Tools |
Live sources (extra) |
|
Knowledge graph (Neo4j) |
|
Extract / doc content / source auth |
|
Parse (file uploads) |
|
Train (file uploads) |
|
KB Sync connectors |
|
KB Sync cc-pairs |
|
KB Sync legacy [deprecated] |
|
Resources (11): lyzr://agents, lyzr://agent/{agentId}, lyzr://kb/{ragId}, lyzr://kb/{ragId}/documents, lyzr://session/{sessionId}, lyzr://workflows, lyzr://workflow/{flowId}, lyzr://a2a-agents, lyzr://a2a-agent/{agentId}, lyzr://traces, lyzr://world-model/{agentId}.
Prompts (6): draft_support_agent, summarize_conversation, setup_rag_agent, draft_guardrail_policy, draft_a2a_agent, audit_agent_activity.
Skipped: KB Sync legacy OAuth/browse/webhooks are implemented but flagged
[deprecated]per the upstream API. Skills (client-side agent skill definitions) have no REST API and remain unwrapped.
How the API key flows
Transport | Key source |
stdio (local install) |
|
Streamable HTTP / SSE (hosted) | per-request header |
The server only reads the key — it never writes it to disk. The client (or the request header) is the secure store.
Build
npm install
npm run build # tsc -> build/index.js
npm test # vitest
npm run lint # biome lint .
npm run format # biome format --write .Requires Node ≥ 18 (uses the global fetch). Get your key from Agent Studio → Account → API Keys.
Add to your coding tool (local, stdio)
All examples run the built entrypoint: node <repo>/build/index.js stdio. Replace /ABS/PATH/lyzr-mcp with your clone's absolute path and YOUR_KEY with your Lyzr API key. (Once published to npm you can swap node <path> for npx -y lyzr-mcp.)
Claude Code
claude mcp add lyzr -e LYZR_API_KEY=YOUR_KEY -- node /ABS/PATH/lyzr-mcp/build/index.js stdioVerify with claude mcp list or /mcp. Add -s user for a global (all-projects) install.
Claude Desktop
~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"lyzr": {
"command": "node",
"args": ["/ABS/PATH/lyzr-mcp/build/index.js", "stdio"],
"env": { "LYZR_API_KEY": "YOUR_KEY" }
}
}
}Fully quit and reopen Claude Desktop; the tools appear under the 🔨 icon.
OpenAI Codex CLI
~/.codex/config.toml:
[mcp_servers.lyzr]
command = "node"
args = ["/ABS/PATH/lyzr-mcp/build/index.js", "stdio"]
env = { LYZR_API_KEY = "YOUR_KEY" }(Or codex mcp add lyzr -- node /ABS/PATH/lyzr-mcp/build/index.js stdio, then set the key in the config's env.) List servers with codex mcp list.
Cursor
~/.cursor/mcp.json (global) or .cursor/mcp.json (per-project):
{
"mcpServers": {
"lyzr": {
"command": "node",
"args": ["/ABS/PATH/lyzr-mcp/build/index.js", "stdio"],
"env": { "LYZR_API_KEY": "YOUR_KEY" }
}
}
}Windsurf
~/.codeium/windsurf/mcp_config.json — same shape as Cursor (mcpServers → command/args/env).
VS Code (GitHub Copilot)
.vscode/mcp.json — note servers and type, and prompt for the key so it lands in the secret store:
{
"inputs": [
{ "type": "promptString", "id": "lyzr-key", "description": "Lyzr API Key", "password": true }
],
"servers": {
"lyzr": {
"type": "stdio",
"command": "node",
"args": ["/ABS/PATH/lyzr-mcp/build/index.js", "stdio"],
"env": { "LYZR_API_KEY": "${input:lyzr-key}" }
}
}
}Add to a hosted server (remote, bring-your-own-key)
Run one shared instance and let each user connect with their own key in a header:
PORT=3001 node /ABS/PATH/lyzr-mcp/build/index.js streamableHttp # endpoint: http://HOST:3001/mcpPut it behind HTTPS (reverse proxy, or ngrok http 3001 for a quick test). Then:
Claude Code:
claude mcp add --transport http lyzr https://your-host/mcp --header "x-api-key: YOUR_KEY"Cursor / Windsurf (mcp.json):
{ "mcpServers": { "lyzr": {
"url": "https://your-host/mcp",
"headers": { "x-api-key": "YOUR_KEY" } } } }VS Code (.vscode/mcp.json): { "servers": { "lyzr": { "type": "http", "url": "https://your-host/mcp", "headers": { "x-api-key": "YOUR_KEY" } } } }
stdio-only clients (Codex CLI, older clients) bridge to the remote server with mcp-remote:
# ~/.codex/config.toml
[mcp_servers.lyzr]
command = "npx"
args = ["-y", "mcp-remote", "https://your-host/mcp", "--header", "x-api-key:YOUR_KEY"]See docs/README.md for Docker + HTTPS deployment.
Skills
This repo ships nine Claude skills — short guides that teach Claude the right way to use this
server's tools (when to use lyzr_chat vs lyzr_stream_chat, how KB training works, when a destructive op
needs confirmation, etc). One skill per capability: lyzr-agents, lyzr-knowledge-base,
lyzr-knowledge-graph, lyzr-memory, lyzr-scheduler, lyzr-guardrails, lyzr-credentials,
lyzr-file-processing, lyzr-kb-sync.
There are two ways to install them, same as Supabase documents for its own agent-skills repo.
Option A: the community skills CLI (repo-agnostic)
Install all skills using the skills CLI, pointed at this
GitHub repo — no dependency on this package being published to npm, just a git checkout of
NeuralgoLyzr/lyzr-mcp:
npx skills add NeuralgoLyzr/lyzr-mcpInstall a specific skill:
npx skills add NeuralgoLyzr/lyzr-mcp --skill lyzr-agentsThis works because skills discovers any skills/<name>/SKILL.md folder with name/description
frontmatter in a repo — the exact layout under skills/ here — and copies the selected
skill(s) into .claude/skills/ (or the equivalent path for whichever coding agent you use).
Option B: the bundled lyzr-mcp-skills installer (zero GitHub dependency)
If you'd rather not depend on cloning this repo — e.g. air-gapped environments, or you just want the skills bundled with the npm package — use the installer shipped alongside this server:
npx lyzr-mcp-skills # interactive checklist
npx lyzr-mcp-skills all # install everything
npx lyzr-mcp-skills lyzr-agents lyzr-knowledge-base # install specific onesBoth install to .claude/skills/<name>/SKILL.md in your current directory.
Layout
src/
index.ts # launcher: argv → dynamic import of one transport
config.ts # per-user key helpers (env / header) + service-URL resolution
lyzr/ # one API client per Lyzr host, all extending LyzrHttp
http.ts # shared base: key, request(), query params, LyzrApiError, ServiceUrls
client.ts # agents + inference (agent host)
agent-extras.ts # sessions + templates (agent host)
rag.ts rag-admin.ts rag-content.ts rag-credentials.ts knowledge-graph.ts (rag host)
memory.ts scheduler.ts rai.ts
<28 more agent-host clients: a2a.ts, workflows.ts, world-model-*.ts, git-agent.ts, ...>
<8 more rag-host clients: kb-sync-*.ts, rag-parse-files.ts, rag-train-files.ts, ...>
server/ # createServer() factory, logging, roots
tools/ # one file per tool-set + index.ts registry (423 tools total)
resources/ # agents/KBs/sessions/workflows/A2A/traces/world-models as resources + subscriptions
prompts/ # reusable prompt templates
cli/ # install-skills.ts — the `lyzr-mcp-skills` installer
transports/ # stdio, sse (deprecated), streamableHttp
__tests__/ # vitest unit tests (one file per lyzr/*.ts client)
skills/ # end-user Claude skills, installed via `npx lyzr-mcp-skills`
.claude/skills/ # contributor-facing skill (lyzr-api-endpoint) for adding new endpointsMaintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Flicense-qualityDmaintenanceA production-ready MCP server built with FastAPI, providing an enhanced tool registry for creating, managing, and documenting AI tools for Large Language Models (LLMs).Last updated34
- AlicenseBqualityAmaintenanceMCP server that exposes any LynxPrompt instance to LLMs, enabling browsing, searching, and managing AI configuration blueprints and prompt hierarchies.Last updated6402GPL 3.0
- FlicenseAqualityFmaintenanceMCP server that exposes 300+ AI agents as tools via a single API key. Supports listing agents, invoking any agent with chat-completion style messages, checking agent health, and retrieving platform statistics.Last updated53

Agorus MCP Serverofficial
Alicense-qualityDmaintenanceMCP server for the Agorus AI agent marketplace, exposing API operations as tools for LLMs to discover, contract, and interact with agents and services.Last updated17MIT
Related MCP Connectors
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
MCP server providing access to the Scorecard API to evaluate and optimize LLM systems.
Local-first RAG engine with MCP server for AI agent integration.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/nandanNM/lyzr-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server