MCP Setup
Enable LyDos in AI IDEs, Cursor, VS Code, GitHub Copilot, and any MCP-compatible AI tool. Run 109 agents and 162 tools directly from your editor conversations.
What is MCP?
The Model Context Protocol (MCP) is an open standard that lets AI assistants directly invoke external tools. By registering LyDos as an MCP server, every conversation in your editor gains access to the full LYDOS agent fleet.
Zero context switching
Ask your AI IDE to run security scans or research tasks — no terminal needed.
109 agents as tools
Every LyDos agent is exposed as a native MCP tool with typed parameters.
Any MCP client
Works with AI IDEs, Cursor, VS Code, GitHub Copilot, and any editor that implements the MCP standard.
Prerequisites
- ✓LyDos CLI — Clone and build with
git clone https://github.com/lydianai/AILYDIAN-AGENT-ORCHESTRATOR.gitthencd AILYDIAN-AGENT-ORCHESTRATOR/cli && go build -o lydos ./cmd/lydos/. Verify withlydos --version. - ✓LyDos Token — Run
lydos loginto authenticate via browser. Your token (prefixlyd_sk_) is saved to~/.lydos/config.jsonand referenced asLYDOS_TOKENin MCP configs. - ✓MCP-compatible client — An AI IDE (recommended), Cursor, or any tool that implements MCP.
Setup Wizard
Install the CLI
| git clone https://github.com/lydianai/AILYDIAN-AGENT-ORCHESTRATOR.git |
| cd AILYDIAN-AGENT-ORCHESTRATOR/cli && go build -o lydos ./cmd/lydos/ |
| # Verify installation |
| lydos --version |
Configure .mcp.json
| { |
| "mcpServers": { |
| "lydos": { |
| "command": "lydos", |
| "args": ["mcp", "serve"], |
| "env": { |
| "LYDOS_TOKEN": "lyd_sk_your_token_here", |
| "LYDOS_API_URL": "http://localhost:8888" |
| } |
| } |
| } |
| } |
.mcp.json and .vscode/mcp.json to .gitignore, or pass the token via a shell environment variable instead of hardcoding it.Place .mcp.json in your project root (per-project) or at ~/.mcp.json for global access. Run lydos mcp install to have the CLI write this file automatically.
Verify the connection
Restart your MCP client, then use the interactive test below or type /mcp in your AI IDE to confirm LyDos is listed.
Test MCP Connection
Verify that the MCP server starts and tools are accessible.
| # Test MCP server manually |
| LYDOS_TOKEN="lyd_sk_your_token" lydos mcp serve |
| # Check health via MCP |
| lydos health --json |
Available MCP Tools
The LyDos MCP server exposes 162 tools spanning Q1–Q248 engines. Once connected, all tools are callable from any MCP-compatible client. In your AI IDE, describe the task in natural language and the assistant selects the right tool automatically.
| Tool |
|---|
lydos_chat |
lydos_agent_run |
lydos_health |
lydos_tasks_list |
lydos_task_get |
lydos_agents_list |
AI IDE Integration
In your AI IDE, you don't need to call tools explicitly. Just describe what you want in natural language and the assistant will select and invoke the right LyDos tool.
“Check LyDos health and tell me the system status”
System health check
lydos_health“Use the security-scanner agent to scan this codebase for vulnerabilities”
Security scan
lydos_agent_run“Research the latest developments in quantum computing using the deep-research agent”
Deep research
lydos_agent_run“List all running LyDos tasks and show me their status”
Task monitoring
lydos_tasks_list“What LyDos tools are available to me right now?”
Tool discovery
lydos_mcp_toolsTroubleshooting
⚠ MCP server not found
- •Verify CLI is installed:
lydos --version - •Check that the command path is correct (try full path: /usr/local/bin/lydos)
- •Restart your MCP client completely after editing .mcp.json
⚠ Authentication failed
- •Verify your token is valid:
lydos auth token - •Re-authenticate:
lydos login - •Ensure LYDOS_TOKEN in the JSON env block exactly matches the token shown by lydos auth token
⚠ Tools available but not responding
- •Test the server health:
lydos health - •Run a quick chat:
lydos chat "ping" - •For local setup, confirm LYDOS server is running on port 8888
Security Best Practices
- ✓Never commit .mcp.json with hardcoded API keys to version control.
- ✓Add .mcp.json to your .gitignore file.
- ✓Prefer reading keys from shell environment variables rather than inline in JSON.
- ✓Rotate tokens regularly — run lydos login to issue a new token and revoke the old one.
- ✓Use project-scoped keys to limit blast radius if a key leaks.
- ✓Audit your active sessions periodically and revoke any tokens no longer in use.
Need help?
Additional resources:
- Getting Started — Quick setup guide
- Agents Guide — Learn about all 109 agents
- CLI Reference — Full command documentation
- SDK Reference — Python SDK (more languages coming soon)
- Community Chat — Coming soon