Install and Configure MCP Servers
The Model Context Protocol (MCP) is how Wayland gains tools beyond the eight built in. An MCP server exposes a set of tools (a database client, a browser, a search API), and once connected those tools become available to your assistants.
Install from the library
Section titled “Install from the library”The fastest path is the in-app MCP Library:
- Open Settings -> MCP Library.
- On the Browse tab, find a server.
- Open its detail page to see what tools it provides.
- Choose Install.
Installed servers appear on the Installed tab, where you can manage or remove them.
Add a server by hand
Section titled “Add a server by hand”To connect a server that is not in the library:
- In Settings -> MCP Library, choose Add server.
- Pick the transport:
- stdio: give the command and arguments that launch the server.
- SSE or streamable-http: give the server URL.
- Add any environment variables or headers the server needs.
- Save.
Sync to assistants
Section titled “Sync to assistants”After installing a server, sync its tools to the assistants that should use them. The same control lets you keep a server’s tools off assistants that do not need them, which keeps each assistant’s tool set focused.
Defer heavy servers
Section titled “Defer heavy servers”A server can be marked deferred so its tool schemas load only when needed rather than at startup. This keeps launches fast when you have many servers connected. The agent finds deferred tools on demand through ToolSearch.
Verify the connection
Section titled “Verify the connection”Once installed, the MCP status display shows whether the server connected and its tools registered. If a server fails to start, check the command and arguments (for stdio) or the URL (for SSE and streamable-http). For more, see MCP Server Issues.
The same in the engine
Section titled “The same in the engine”Wayland Core connects to the same servers through config rather than a UI. Define them under [mcp.servers.*] in your config file. See Configuration for the format.