MCP Servers

Akio supports the Model Context Protocol (MCP), which lets it connect to external tool servers and use their tools during inference. MCP servers are registered once and automatically reconnected every session.

Server configurations are persisted in ~/.akio/mcp.json.

---

Adding a server

Register an MCP server with akio mcp add:

akio mcp add --name <name> --command <command> --args <args...>

Flag	Description
--name	Friendly name used to reference the server
--command	Executable to spawn (e.g. uvx, node, npx)
--args	Arguments forwarded to the command

Example — browser-use

akio mcp add \
  --name browser-use \
  --command uvx \
  --args "--from" "browser-use[cli]" "browser-use" "--mcp"

---

Listing servers

akio mcp list

Displays all registered servers. For each reachable server, the available tools are shown:

browser-use (uvx browser-use)
  - `browser_navigate` - Navigate to a URL
  - `browser_click` - Click on an element by index
  - ...

---

Removing a server

akio mcp remove <name>

akio mcp remove browser-use

---

How it works

Akio spawns each registered MCP server as a child process and communicates with it over stdio using the MCP protocol. When a session starts, all registered servers are connected and their tools are made available to the agent. The agent can call these tools during inference just like built-in tools.

akio run -m Qwen3-8B-Q4_K_M.gguf
  └─ spawns: uvx browser-use   (stdio)
  └─ spawns: npx @modelcontextprotocol/server-filesystem /tmp   (stdio)

---

Configuration file

The registry is stored at ~/.akio/mcp.json. You can edit it directly if needed:

{
  "servers": [
    {
      "name": "browser-use",
      "command": "uvx",
      "args": ["--from", "browser-use[cli]", "browser-use", "--mcp"]
    }
  ]
}