Add an MCP server
2 min · 6 steps
Click 'Add MCP server' on Settings → AI → MCP Clients, pick the transport (stdio or HTTPS) + auth, and Avery creates the connector and opens the connection in one step.
The fastest way to add an MCP server is right on Settings → AI → MCP Clients: click 'Add MCP server', fill the form, and Avery both saves the connector AND opens the live connection in a single step — you never have to leave the screen. The form asks for a name, the transport (stdio runs a child process on this machine; Streamable HTTP opens an HTTPS connection to a remote endpoint), and an optional bearer token. Behind the scenes this writes a normal `mcp-server` connector (so the bearer token lands in the OS keystore and the agent builder can bind it), then runs the handshake. You can also add MCP servers from the Connectors page like any other connector if you prefer to manage everything in one place — both routes produce the same connector.
Steps
- Open Settings → AI → MCP Clients.
Sidebar → Settings → AI tab → 'MCP Clients' sub-tab (this is where Avery is the client connecting OUT to other servers). Click the 'Add MCP server' button.
- Name the server.
Give it a short name like 'EODHD', 'GitHub', or 'Postgres'. The name doubles as the slug in the tool ids your agents will see (`mcp.<slug>.<tool>`).
- Pick the transport.
stdio for local servers Avery spawns as a child process (the default for `@modelcontextprotocol/server-*` npm packages). Streamable HTTP for remote servers you reach over HTTPS.
- Fill the per-transport fields.
stdio: command + arguments (one per line) + optional env vars (use `{{secret}}` to substitute the bearer token). Streamable HTTP: the endpoint URL + per-request timeout.
- Add a bearer token if the server needs one.
Most stdio servers need none. Remote HTTPS servers usually want an Authorization: Bearer header — switch Auth to 'Bearer token' and paste the value. It's stored encrypted in the local keystore.
- Click 'Add + connect'.
Avery creates the connector and immediately opens the connection. On success the new row turns green and the tool count appears — no separate Connect step needed. If the connection fails, the connector is still saved and the row shows a 'Connect' button so you can retry.
Live recipes need the desktop
This article is a static preview. The in-app Help sidecar inside Avery NXR can fire each step against your live project — install the desktop to use it interactively.