Custom MCP Server

Custom MCP connectors let you connect Sazabi to any MCP-compatible server. This enables integration with internal tools, self-hosted services, or any MCP server not covered by Sazabi's pre-configured connectors.

About custom connectors

Custom connectors work the same as pre-configured connectors, but you provide the server URL and authentication details. Once connected, Sazabi discovers the available tools and makes them available to Chat.

Prerequisites

Before connecting a custom MCP server, make sure you have:

A Sazabi account with admin permissions.
The MCP server URL (must be HTTPS).
Authentication credentials (if required by the server).

Connecting a custom server

Open MCP Connectors

Go to Settings -> MCP Connectors in the Sazabi dashboard.

Add custom server

Click Add Custom Server at the bottom of the connectors list.

Configure connection

Enter the server details:

Name: A display name for the connector (e.g., "Internal Tools")
URL: The MCP server URL (e.g., https://mcp.internal.example.com/mcp)
Authentication: Configure headers if the server requires authentication

Test and save

Click Connect to test the connection. If successful, Sazabi will discover and display the available tools.

Authentication options

Custom MCP servers can use header-based authentication. Add custom headers that will be sent with every request to the server.

Adding headers

Click Add Header in the authentication section.

Enter the header name (e.g., Authorization, X-API-Key).

Enter the header value (e.g., Bearer your-token, your-api-key).

You can add multiple headers if your server requires them.

Header values are encrypted at rest. However, anyone with admin access to your Sazabi organization can configure connectors and see tool outputs.

Server requirements

Your MCP server must:

Be accessible over HTTPS
Implement the MCP protocol specification
Return tool definitions that Sazabi can discover
Respond to tool calls with valid MCP responses

Example: Internal API gateway

If your organization has an internal MCP server that exposes tools for your infrastructure:

Name: Internal Infrastructure
URL: https://mcp.internal.acme.com/mcp
Headers:
  X-Internal-Token: your-internal-token

Once connected, you can ask Sazabi to use tools from your internal server:

Use the internal tools to check deployment status
What does the internal API show for service health?

Troubleshooting

Connection failed

If the connection fails:

Verify the URL is correct and accessible from the internet.
Check that the server uses HTTPS.
Verify any authentication headers are correct.
Check server logs for connection attempts.

No tools discovered

If no tools are found:

Verify the server implements MCP tool discovery correctly.
Check that the server returns tools in the expected format.
Try accessing the server's tool list endpoint directly.

Tool calls failing

If tools are discovered but calls fail:

Check that authentication is still valid.
Verify the tool parameters are correct.
Check server logs for errors.

Updating a custom connector

To update a custom connector's configuration:

Go to Settings -> MCP Connectors.
Click on the custom connector.
Update the URL or headers.
Click Save to apply changes.

Sazabi will rediscover tools after saving.

Disconnecting a custom connector

To disconnect a custom MCP server:

Go to Settings -> MCP Connectors.
Click on the custom connector.
Click Disconnect and confirm.