SoAI uses the Model Context Protocol in two independent directions. In host mode, SoAI connects to
external MCP servers and can use what they publish. In server mode, authenticated MCP clients
connect to SoAI at /mcp. Both modes can run at the same time.
Choose the direction
| Goal | SoAI's role | Continue with |
|---|---|---|
| Use tools, resources, or prompts from another MCP service in SoAI conversations | Host or client | Connect MCP servers to SoAI |
| Give an IDE, coding agent, or other MCP client selected SoAI capabilities | Server | Use SoAI as an MCP server |
Configure MCP access
In the SoAI WebUI, select the Settings button at the right of the header, then Settings > MCP. The tab requires an
Administrator with
MCP administration
(MCP_ADMIN). It contains runtime status, configured
servers, connections, resources, prompts, tools, pending interactions, client roots, search-provider keys, and MCP
tokens. Reading runtime status and the Resources, Prompts, and Tools panels also requires
MCP usage (MCP_USE).
MCP configuration also requires
Configuration changes
(CONFIG_PATCH).
The global MCP runtime, host mode, and server mode are enabled by default. A connection or server exposure can still be unavailable because its own feature switch, authentication, permission, provider, or runtime requirement is not satisfied.
Keep credentials separate
An MCP token authenticates requests to /mcp, but it cannot sign in to the WebUI or authenticate
/v1/*. SoAI API keys likewise do not authenticate MCP, so issue one MCP token per client and revoke it
when that client no longer needs access.
Understand runtime and policy boundaries
A connected external server runs its operations where that server is hosted. A tool exposed by SoAI server mode runs on the SoAI host with the operating-system identity and permissions of the SoAI process. Tool visibility and protocol discovery do not by themselves make a tool safe for every user or client. Keep exposure lists narrow and follow Security hardening for high-impact capabilities.
Messaging uses a separate policy layer
Discord, Telegram, and WhatsApp accounts have their own Chat, Plan, and Execute tool selections under Settings > Messaging > Edit > MCP tools and approval. Their conversations inherit those selections, so Chat locks the corresponding controls. See Connect messaging apps to SoAI for sender access and remote approval behavior.
SoAI's skills use the conversation-scoped skill_read tool to load selected
instructions and supporting text. This does not publish the account's skill library through the MCP server.
External clients and connected servers keep their own instruction and resource boundaries.