Custom MCP Server

Add your own MCP (Model Context Protocol) server as a connector so your AI environment can call its tools through Waldium. You control the server URL, authentication, and which tools are enabled.

You need a running MCP server that speaks the MCP protocol. This page covers how to register and configure it in Waldium under Settings → Extensions → Connectors.

When to use a custom connector

Use a custom connector when:

You run an MCP server yourself (e.g. internal APIs, scripts, or data sources).
You use a third-party MCP server that isn’t in Waldium’s curated connector list.
You want to expose a subset of tools and manage them from the Waldium dashboard.

Adding a custom connector

In the Waldium dashboard, go to Settings → Extensions → Connectors.
Open the Custom connector card (or Add custom / New custom connector).
Fill in the form:
- Name — A label for this connector (e.g. “Internal API”, “Docs MCP”).
- URL — The MCP server URL your AI client would use (e.g. https://your-mcp.example.com/mcp or a local endpoint if supported).
- Authentication — If your server requires auth, use the provided fields (e.g. API key, header name/value). Exact options depend on the Connectors UI; common patterns are:
  - API key in a header (e.g. Authorization: Bearer <key>).
  - Custom header name and value.
Click Test to check that Waldium can reach the server and get the list of tools.
In the tools list, enable only the tools you want to expose to your AI for this site.
Save the connector.

After saving, the custom connector appears in the Connectors list. You can open its detail view to change the URL, auth, or tool toggles, or disconnect it.

Server requirements

Your MCP server should:

Be reachable from Waldium’s infrastructure (public URL or allowed network).
Implement the Model Context Protocol so that:
- Waldium can discover tools (and optionally resources).
- Requests from Waldium (or from your AI environment via Waldium) are in the format the server expects.

If the server uses auth, configure the same credentials in the custom connector so Waldium can call it for testing and for proxying tool calls.

Testing the connection

Use the Test button on the custom connector form (or detail page) to:

Verify Waldium can reach the server URL.
Confirm authentication works.
Fetch the list of tools the server exposes.

If the test fails, check:

URL — Correct scheme (e.g. https), host, and path.
Auth — Correct API key or headers; no extra spaces or wrong header names.
Server — Server is running and responding; firewall or network allows Waldium to connect.

Managing tools

On the custom connector’s detail page you can:

See all tools reported by the server.
Enable or disable each tool with a toggle.

Only enabled tools are available to your AI for this site. Disable tools you don’t want to expose or that you’re not ready to use.

Connectors — Overview of connectors and the Connectors settings page.
MCP integration — How Waldium uses MCP and authentication.