docs/guides/mcp-setup.md
MCP lets Agent Zero use tools from other apps and services.
Think of each MCP connection as a bridge. One bridge might connect Gmail, another might connect a database, and another might connect an automation app.
Use MCP when you have a clear external tool you want Agent Zero to call. For normal browsing, start with Agent Zero's built-in Browser first.
[!NOTE] This page is about giving Agent Zero tools from other apps. For deeper MCP details, see the advanced MCP reference.
| Need | Good first stop |
|---|---|
| Browse, screenshot, annotate, or use the Docker browser | Browser Guide |
| Use your host Chrome-family browser through A0 CLI | A0 CLI Connector |
| Connect a third-party app or service with MCP support | This guide |
| Paste or review MCP JSON by hand | Advanced MCP Configuration |
The configuration editor accepts JSON. A command-based MCP connection looks like this:
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": ["-y", "chrome-devtools-mcp@latest"]
}
}
}
Click Apply now after editing.
[!TIP] The first launch of an
npxoruvxserver can take a little longer because the package may need to download.
After applying the config, look for the status below the editor.
| Signal | What it means |
|---|---|
| Name | The connection Agent Zero found. |
| Tool count | How many tools are available. |
| Green status | The connection is working. |
| Error text | The command, URL, network, or credentials need attention. |
MCP tools become available automatically after the connection works.
You can still ask naturally:
Use the connected Gmail tools to find the last message from Alice and summarize it.
Use this pattern when Agent Zero should start the tool itself.
{
"mcpServers": {
"sqlite": {
"command": "uvx",
"args": ["mcp-server-sqlite", "--db-path", "/root/db.sqlite"]
}
}
}
Use this pattern when the tool is already running at a URL.
{
"mcpServers": {
"external-api": {
"url": "https://api.example.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}
[!IMPORTANT] Do not paste real API keys into public files, screenshots, or issue reports. Prefer project secrets or environment variables when possible.
If Agent Zero runs in Docker and the MCP tool runs somewhere else, the address matters.
| Where the MCP tool runs | What to use from Agent Zero |
|---|---|
| Host machine on macOS or Windows | host.docker.internal |
| Another container | Same Docker network plus the container name |
| Remote server | The reachable HTTPS URL |
| Inside Agent Zero's container | Local command config |
On Linux, host.docker.internal is not always available by default. Running the
MCP tool in the same Docker network is usually cleaner.
For most browsing tasks, use Agent Zero's built-in _browser plugin and direct
browser tool. It covers the Docker browser surface, screenshots, annotations,
Chrome extensions, and optional A0 CLI host-browser mode.
MCP-based browser tools are still useful when another browser tool is required for a specific workflow.
See the Browser Guide for the built-in workflow.
| Tool type | Useful for |
|---|---|
| Chrome DevTools MCP | Direct Chrome debugging/control workflows |
| Playwright MCP | Alternative browser automation stacks |
| n8n MCP | Workflow automation |
| Gmail MCP | Email workflows |
| VS Code MCP | IDE-centered workflows |
host.docker.internal on macOS or Windows.