Connect MCP servers to Multify
What You Need
Multify connects to remote MCP servers reachable over the internet: anything that speaks the Model Context Protocol over Streamable HTTP or SSE at an https:// URL, plus any auth headers it requires.
"command" and "args" (local stdio servers) are skipped automatically. Use a server that exposes a remote https URL instead.
Where to Add MCP Servers
You can add and manage MCP servers on web and desktop. On mobile, any servers you've added work in chat automatically, but they can't be added or managed there.
Sign in at app.multify.co, click your profile icon (top-right), and choose Add MCP Servers to Chat, or go directly to app.multify.co/app/mcp-servers.
Open Settings, find the MCP Servers section, and click Manage.
Adding a Server
There are two ways to add a server.
Paste an MCP configuration block and click Parse & preview. Multify extracts the servers, shows you what it will add (and anything it skipped, like stdio servers), and even auto-corrects slightly malformed JSON. Then click Add servers.
{
"mcpServers": {
"my-server": {
"url": "https://example.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_TOKEN"
}
}
}
}
Fill in a Name, the server's https URL, and (optionally) any headers as JSON, for example an Authorization bearer token. Click Add server.
Testing a Connection
Each server in your list has a Test button. It performs a live handshake with the server and reports how many tools it found, or a clear error if it couldn't connect. The status badge updates to Connected or Error so you can tell at a glance which servers are healthy.
Enabling & Deleting
- Enable / Disable: temporarily turn a server's tools on or off in chat without removing it.
- Delete: remove a server entirely. You'll be asked to confirm first; once deleted, its tools are no longer available in chat.
Using MCP Tools in Chat
That's it — no extra step. When you chat with your Multify assistant, the tools from your enabled MCP servers are available automatically on every device. Just describe what you want in plain English; the assistant decides when to call an MCP tool, the same way it uses Multify's built-in tools. Because tools are namespaced per server, multiple servers can coexist without clashing.
Security
Multify only connects to public https endpoints and blocks attempts to reach internal or private network addresses. Your auth headers are stored securely and are never shown back to you in plain text after you save them. A server that's slow or unreachable is simply skipped for that message — it never breaks your chat.
Troubleshooting
My server was skipped when I added it
The most common reasons: it used a local command/stdio setup (not supported — use a remote URL), the URL wasn't https, or the URL pointed at a private/internal address. The preview lists the exact reason next to each skipped server.
Test connection fails
Double-check the URL and that any required auth header is correct (e.g. Authorization: Bearer …). Confirm the server is an MCP endpoint that supports Streamable HTTP or SSE and is reachable from the public internet.
Tools aren't showing up in chat
Make sure the server is Enabled and that Test reports tools. Try a fresh message after enabling it. If a server recently changed its tools, run Test again to refresh Multify's cached tool list.