Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

MCP

Model Context Protocol (MCP) lets Veyyon connect to external tools and data sources. Veyyon is an MCP client by default; agent control protocol (ACP) and SDK paths can expose Veyyon as a server.

Transports

TransportUse when
stdioLocal executable (Node, Python, binary)
HTTP / SSERemote hosted MCP service

Configure servers

Preferred: JSON files managed by Veyyon:

ScopePath
Project.veyyon/mcp.json
User~/.veyyon/agent/mcp.json

Example:

{
  "$schema": "https://raw.githubusercontent.com/can1357/oh-my-pi/main/packages/coding-agent/src/config/mcp-schema.json",
  "mcpServers": {
    "sqlite": {
      "type": "stdio",
      "command": "node",
      "args": ["/path/to/sqlite-mcp/index.js"],
      "env": { "DB_PATH": "/var/data/app.db" }
    }
  }
}

Veyyon also discovers MCP entries from Claude, Cursor, VS Code, OpenCode, and related tool configs.

Setup walkthrough: MCP server setup.

Engineering detail: docs/mcp-config.md.

In the TUI

CommandPurpose
/mcpList servers, connection/auth status, exposed tools
/mcp addAdd a server (wizard)
/mcp listList configured servers
/mcp remove <name>Remove a server
/mcp test <name>Test connectivity
/mcp reauth <name>Refresh OAuth

Tool names appear namespaced as mcp__<server>__<tool>.

Running Veyyon as an MCP server

Use the ACP integration or SDK embedding rather than a separate veyyon mcp-server subcommand unless your build registers it.

Spec — not shipped: a [mcp_servers.*] config table and a veyyon mcp CLI. Veyyon configures MCP through mcp.json and the /mcp command instead.