Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"verlon": {
"env": {
"VERLON_API_KEY": "sk-vrln-..."
},
"args": [
"-y",
"@verlon-ai/mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Model Context Protocol server for Verlon AI. Exposes your Verlon resources (gates, logs, recommendations, experiments) as MCP tools so coding agents — Claude Code, Cursor, Cline, any MCP-compatible client — can inspect and manage your AI infrastructure natively.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@verlon-ai/mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @verlon-ai/mcp against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Pi Coding Agent extension (CLI-first) — routes bash/read/grep/find/ls through lean-ctx CLI for strong token savings. Optional MCP bridge can register advanced tools.
Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.
97% token reduction for AI coding sessions — zero deps, 21 languages, MCP server
App framework, testing framework, and inspector for MCP Apps.
MCP Security Weekly
Get CVE alerts and security updates for ai.verlon/mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Model Context Protocol server for Verlon AI. Exposes your Verlon resources (gates, logs, recommendations, experiments) as MCP tools so coding agents — Claude Code, Cursor, Cline, any MCP-compatible client — can inspect and manage your AI infrastructure natively.
Status: 0.3.2 — listed in the MCP Registry as ai.verlon/mcp. Ships 5 read-only tools (list_gates, get_gate, list_logs, get_recommendations, list_experiments). Write tools (create_gate, update_gate, run_chat, start_experiment) gated behind --enable-writes land in a future release.
You don't install it directly. Your MCP client (Claude Code, Cursor, etc.) spawns it as a subprocess via npx. Add the snippet below to your client's MCP config.
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or the equivalent on your OS:
{
"mcpServers": {
"verlon": {
"command": "npx",
"args": ["-y", "@verlon-ai/mcp"],
"env": {
"VERLON_API_KEY": "sk-vrln-..."
}
}
}
}
Then restart Claude Code. The verlon server should appear in the tools list, and Claude can call verlon:list_gates against your account.
Add to your Cursor MCP config (Settings → Features → MCP Servers):
{
"mcpServers": {
"verlon": {
"command": "npx",
"args": ["-y", "@verlon-ai/mcp"],
"env": {
"VERLON_API_KEY": "sk-vrln-..."
}
}
}
}
The server speaks MCP over stdio. Spawn npx -y @verlon-ai/mcp with VERLON_API_KEY in the subprocess environment.
All v0.3.x tools are read-only — see Security note for the rationale and the planned write-tool opt-in.
| Tool | Inputs | What it returns |
|---|---|---|
list_gates | none | Every gate in the account — id, name, description, model, taskType, taskSubtype, createdAt |
get_gate | gateId (UUID) | Full gate config — model, fallback chain, task type, spending limits, sub-gates, orchestration |
list_logs | gate?, since? (ISO 8601), success?, limit? (1-100, default 20) | Recent request logs — timestamp, gate, model, cost, latency, success/failure |
get_recommendations | gateId (UUID) | Cortex intelligence report — themes, drift detection, optimization recommendations. { report: null } when no run has been produced yet |
list_experiments | gateId?, status?, projectId? | Experiments (shadow + split) — id, name, status, test type, variants, goal metric, configuration |
| Env var | Required | Default | Notes |
|---|---|---|---|
VERLON_API_KEY | Yes | — | Your Verlon API key (sk-vrln-...). |
VERLON_BASE_URL | No | https://api.verlon.ai | Override for self-hosted Verlon. |
| Flag | Purpose |
|---|---|
--enable-writes | Register write-capable tools. Phase 3+ feature. In 0.1.x this flag is accepted but no write tools exist yet. Default is read-only — a misaligned agent can't accidentally destroy resources. |
--help, -h | Print usage. |
Read-only by default is a deliberate choice. The MCP client (Claude Code, Cursor, etc.) sees this server's tools and may invoke them autonomously when a user's request makes them seem relevant. A read-only default means even a misaligned agent can only inspect your account, not modify it. Opt in to write tools (--enable-writes, Phase 3+) only after you understand the implications.
npm install
npm test # vitest
npm run build
... [View full README on GitHub](https://github.com/verlon-ai/mcp#readme)