Skip to main content
The Custom MCP Server integration connects the Ryze agent to any remote MCP (Model Context Protocol) server. MCP is an open standard for exposing tools to AI agents — if a service speaks MCP, the Ryze agent can use its tools alongside your marketing accounts: look up documentation, query an internal database, or act on a third-party service. This is the reverse of the Ryze MCP server: that one exposes Ryze to Claude and ChatGPT; this one pulls outside tools into the Ryze agent.

​
Connect a server

1

Open the connect dialog

Open Integrations in the left sidebar, find Custom MCP Server and click Connect.
2

Enter the server details

Give the connection a Name (so you can tell your servers apart) and paste the Remote MCP server URL — the HTTPS address where the server accepts MCP requests, for example https://your-server.com/mcp.
3

Click Add

Ryze connects to the server and reads its tool list. If the server requires sign-in, you are redirected to its authorization page — approve access and you land back in Ryze, connected. Open servers connect immediately.
The card then shows Connected. Click View to see the connection, labelled with the name you gave and the server’s host.
The Advanced settings fields (OAuth Client ID and Secret) are only needed for servers that don’t support automatic client registration. Most servers do — leave them empty unless the server’s documentation says otherwise.

​
Requirements

  • HTTPS only — the server must be reachable at a public https:// URL. Local servers (localhost, private networks) are not supported; expose them through a tunnel if you need to test one.
  • Remote transport — the server must speak MCP over Streamable HTTP, the current standard for remote servers. Local stdio servers cannot be connected.
  • Auth — open servers and OAuth-protected servers both work. OAuth sign-in, token storage, and refresh are handled for you; tokens are stored encrypted.

​
How the agent uses it

After connecting, the agent gets two tools — List tools and Call tool — and picks the right server by name when you have several:
  • List tools — reads the server’s catalog: each tool’s name, description, and input schema
  • Call tool — runs one of those tools with arguments matching its schema
Ryze can’t tell which of the server’s tools only read data, so every Call tool counts as a change. By default the agent runs its tools on its own: the Tool approvals setting in the chat composer starts on Skip all approvals. To review changes before they happen, switch it to Approve write & delete (reads run freely, changes need approval) or Manual approve (every tool that touches your data needs approval). Scheduled tasks run without an approval step.

​
Multiple servers

You can connect as many servers as you need. To add another one, click View on the Custom MCP Server card, then Add one more account, and fill in the new server’s details. Each server is a separate connection, shown in the View window with its name and host. The agent tells them apart and picks the right one for each call.

​
Finding MCP servers

The MCP project maintains an official registry of published servers at registry.modelcontextprotocol.io. Many services also document their MCP endpoint directly — search the service’s docs for “MCP”. Public servers you can try right now, no sign-in needed:

​
Example: Lovable

Lovable’s MCP server lets the Ryze agent work on a Lovable project for you: read its files, send build instructions to Lovable’s own agent, and publish.
  1. Connect with the URL https://mcp.lovable.dev and leave Advanced settings empty.
  2. Approve Ryze AI on the Lovable sign-in page. You land back in Ryze with the server’s tools listed (list_projects, read_file, send_message, deploy_project and more).
  3. In chat, try “List my Lovable projects” or “Ask Lovable to add a pricing section to my landing page”.
send_message and create_project hand work to Lovable’s agent and consume your Lovable credits. Set Tool approvals to Approve write & delete if you want to approve each call first. Changes go live only after deploy_project.

​
Troubleshooting

“Must be a public https:// MCP server URL.” The URL is plain HTTP, points at localhost or a private address, or isn’t a valid URL. Use the server’s public HTTPS endpoint. Connect fails immediately. The URL doesn’t answer MCP requests — check the server’s docs for the exact MCP endpoint path (often ending in /mcp). “This server does not support automatic client registration.” Open the server’s developer settings, create an OAuth client with redirect URL https://reports.get-ryze.ai/api/auth/mcp-server/callback, and enter its Client ID and Secret under Advanced settings. “This MCP server only accepts OAuth clients it has registered in advance, and Ryze is not on its list yet.” The server allows neither automatic client registration nor an unregistered client. Ask the server’s vendor to register Ryze as an MCP client with the redirect URL https://reports.get-ryze.ai/api/auth/mcp-server/callback, then enter the Client ID and Secret they give you under Advanced settings. “This connection attempt expired — try connecting again.” More than 10 minutes passed on the server’s sign-in page. Start again and click Add. Tools stopped working. The server may have revoked access — disconnect and reconnect to re-authorize.