The verified MCP library covers the most common platforms. But your stack might include tools that are not on the list - internal systems, niche platforms, or services your engineering team has built MCP support for themselves.

Your engineering team built MCP support into your internal ticketing system six months ago. It is not on the verified list - it is yours, it is custom, and it is exactly what your agent needs to create and update tickets during customer conversations. You have the server URL. That is all you need.

Adding a custom MCP server by URL connects your agent to any MCP-compatible platform, not just the ones Outlearn has tested. Paste the URL, connect, and your agent gains access to whatever capabilities that server exposes.

In this article, you'll learn:

• When to use a custom MCP server instead of a verified one
• How to add a custom MCP server by URL
• What to expect after connecting

When to Use This

Use a custom MCP server when:

• You've built your own internal MCP server for proprietary tools or systems
• The platform you want to connect isn't on the verified MCP servers list
• You want to extend your agent's capabilities beyond what standard integrations offer

If the platform you need is on the Verified MCP Servers list, use that instead - it's simpler and pre-configured. See Connecting a Verified MCP Server.

What You'll Need

Before adding a custom MCP server, you'll need:

• The MCP Server URL - the full URL of your MCP server endpoint
• A name for the connection - used to identify it in your Actions list
• Any authentication or access credentials required by your server (these are typically configured on the server side, not in Outlearn)

If you're not sure whether your server is MCP-compatible or what URL to use, check with the person on your team who built or manages it.

How to Add a Custom MCP Server

1. Go to the Actions tab.
2. Click + Create Action.
3. In the Create an Action modal, scroll to the MCP Server section.
4. Click the Add MCP Server by URL tab.
5. Enter:
   • MCP Name: A label for this server (e.g., "Internal Inventory System").
   • MCP Server URL: The full URL of your MCP server.
6. Click Connect.

Once connected, your agent will have access to the capabilities your MCP server exposes. Configure the trigger and response handling as you would for any other action.

Best Practices

• Give your custom MCP server a descriptive name that makes it clear what system it connects to - "Custom MCP Server" is harder to manage than "Internal CRM API".
• Test the connection thoroughly in the Preview panel before going live - custom servers can behave differently depending on how they're built.
• Make sure your MCP server is reliable and has appropriate uptime - if it goes down, any actions that depend on it will fail during live conversations.
• Work with your technical team to ensure the server handles errors gracefully and returns clear responses that your  can interpret and communicate to users.