MCP and clients
tavero mcp is an MCP server on stdio for one project: the current folder, or the one passed with --dir. It gives the agent nine tools, so it can run the whole loop without a shell. The tools are listed in For agents.
Connect your client
Print the config for your client and paste it into the file it names. Nothing is written for you.
npx tavero mcp --print-config claude
The clients are claude, cursor, codex, gemini, antigravity, vscode and windsurf. Each tab below is the output of that command.
// .mcp.json
{
"mcpServers": {
"tavero": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"tavero",
"mcp"
]
}
}
}// .cursor/mcp.json
{
"mcpServers": {
"tavero": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"tavero",
"mcp"
]
}
}
}// .codex/config.toml (trusted project) or ~/.codex/config.toml
[mcp_servers.tavero]
command = "npx"
args = ["-y", "tavero", "mcp"]
startup_timeout_sec = 60
tool_timeout_sec = 900// .gemini/settings.json
{
"mcpServers": {
"tavero": {
"command": "npx",
"args": [
"-y",
"tavero",
"mcp"
],
"timeout": 900000
}
}
}// .agents/mcp_config.json
{
"mcpServers": {
"tavero": {
"command": "npx",
"args": [
"-y",
"tavero",
"mcp"
]
}
}
}// .vscode/mcp.json
{
"servers": {
"tavero": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"tavero",
"mcp"
]
}
}
}// ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"tavero": {
"command": "npx",
"args": [
"-y",
"tavero",
"mcp",
"--dir",
"/your/app"
]
}
}
}Add --dir frontend to the arguments when the app lives in a subfolder.
Timeouts
A full scan takes minutes. The Codex and Gemini CLI configs set longer tool timeouts for that reason. After a fix the agent passes routes and rules to tavero_scan, which takes seconds. Scans stream progress, run one at a time and can be cancelled. A dev server the tool starts stays up for later scans.
Windows
Codex is a native binary and may not resolve the npx shim on Windows, so the Codex config printed on native Windows runs npx through cmd /c. The other clients use npx directly.
Logins
Logging in stays a human step. If pages land on a login screen, the scan says so, and a person runs tavero login in a terminal once.