Skip to main content
A custom MCP server is any remote server that speaks the Model Context Protocol and isn’t already in the Vibely catalog. Connect one as a chat connector, and the agent can call its tools while it builds: an internal CRM, a private API, a company knowledge base, or a niche third-party tool.
Connect a custom MCP server
Custom MCP servers are available on all plans. Like every chat connector, they’re personal to you and never part of your published app. If your published app needs to call a service while people use it, ask the agent to integrate the API directly, or have an admin register a custom REST connector.

​
How to connect a custom MCP server

You need the server’s HTTPS URL and, depending on the server, a credential. There are two places to add one.
The quickest way, for servers that sign you in with OAuth or need no credentials.
1

Open the form

Open Customize → Connectors and click Add. The Add custom connector dialog opens.
2

Name the server

Enter a Name, for example acme-crm. It’s shown in the connectors list and saved as a lowercase slug.
3

Enter the URL

Enter the MCP server URL, the HTTPS address where the server accepts MCP requests, for example https://mcp.example.com/mcp.
4

Add it

Click Continue. The server appears in the catalog under the Custom category. Open it to connect and to see the tools it offers.
To confirm it works, ask the agent something only the server can answer:
Only connect servers from developers you trust. Vibely doesn’t control which tools a server offers and can’t verify that they work as intended or won’t change. The agent reads the server’s responses as context, so a malicious server can try to steer it.

​
Requirements

  • The URL must be reachable from the public internet. Vibely refuses URLs that point at localhost or private network addresses.
  • Use an HTTPS URL. The Customize → Connectors form only accepts https://.
  • Each server name must be unique in your account.

​
What the agent can do with it

Once connected, the agent can call the server’s tools during your builds, in any of your projects. The same approval rules apply as for catalog connectors: read-only tools run without asking, while tools that create, change, delete, or send something ask for your approval first.
Connect a custom MCP server

​
Manage custom MCP servers

  • Remove a server: in Settings → Connectors, click Remove next to it. This deletes its stored API key or OAuth token.
  • Change the URL or credentials: remove the server and add it again.
  • Workspace controls: on the Business plan, an admin can turn off Remote MCP connectors in Settings → Privacy & security. That withholds every MCP server, custom ones included, from the agent across the workspace. See Admin controls.

​
FAQ

All plans. The workspace-wide Remote MCP connectors switch that turns them off requires Business.
No. A custom MCP server only gives the agent context while it builds. For functionality in your published app, ask the agent to integrate the service’s API, or use an app connector.
No. MCP servers are stored against your own account. Teammates add the same server themselves with their own credentials.
No. Vibely’s backend connects to the server, so it has to be reachable over the public internet. Local and private-network addresses are refused.