Connect Custom MCP server
Add any remote MCP server by URL, with an optional Authorization header; servers that require OAuth are detected and turn into a sign-in.
Any remote MCP server (Streamable HTTP or SSE) with an optional auth header.
An MCP server is a web service that offers tools (search this, create that) which an agent can call over the Model Context Protocol. Add one and every agent in the workspace can use its tools. Use this when the service you want is not in the Marketplace, or when you run your own server.
Before you start
- The server's URL, reachable from the internet over HTTPS. Localhost or private-network servers will not work.
- Its transport: Streamable HTTP (the current standard, URLs often end in
/mcp) or the older SSE (often/sse). - If the server needs a key, the header value it expects.
- You must be an owner or admin in your woble workspace.
Connect it
- Open Marketplace in the sidebar, switch to the Integrations tab, find Custom MCP server at the bottom and press Add.
- Enter a Name, how it shows up for agents: Internal wiki, Acme API.
- Paste the Server URL.
- Pick the Transport: Streamable HTTP or SSE.
- In Auth header value (optional) paste what the server expects in its
Authorizationheader, such asBearer <token>. For an open server leave it empty. - In How agents should use it write a sentence or two: which tool to call first, what needs your approval.
- Press Connect. Woble asks the server for its tool list. If the server requires OAuth, woble discovers its sign-in settings automatically and the step turns into a sign-in: a new tab opens at the server's login page, you approve, the tab closes.
- The card shows Connected and the agent panel lists the new tools.
Or ask an agent
Type @ruby connect the MCP server at https://example.com/mcp in any chat. The same card appears there. Only an owner or admin can complete it.
Try it
- "@atlas use the Acme API server to look up order 1042 and tell me its status."
If it does not connect
- Wrong transport. Streamable HTTP treated as SSE (or the reverse) fails with a protocol or 404 error. Switch it and try again.
- Header value wrong or expired. Most servers want
Bearer, a space, then the token. Regenerate it and Remove + reconnect. - The server is not reachable from the internet or allowlists callers. Test connection in Marketplace, then Connected, shows the exact error; pass it to whoever runs the server.
Disconnect
Open Marketplace, then Connected, and press Remove next to the server. The stored header or tokens are deleted and agents lose its tools immediately.