> ## Documentation Index
> Fetch the complete documentation index at: https://docs.superlog.sh/llms.txt
> Use this file to discover all available pages before exploring further.

# Custom MCP servers

> Connect any remote MCP server so automations and tag mode can use its tools.

Connect your own remote MCP server to give agents tools Superlog does not have built in, such as an internal admin API or a data source you host.

## Requirements

* The server uses the Streamable HTTP transport.
* The URL uses HTTPS and resolves to a public address.
* Authentication is an API token, or OAuth 2.0 with authorization-server discovery, PKCE, and dynamic client registration.

## Add a server

<Steps>
  <Step title="Open the dialog">
    In **Integrations**, click **Add** on **Custom MCP**. Or, in the automation connector picker, click **Add custom MCP server**.
  </Step>

  <Step title="Enter the server details">
    Enter a **Name** and the **Streamable HTTP URL**.
  </Step>

  <Step title="Choose authentication">
    Choose **API token** and paste the token, or choose **OAuth 2.0** and click **Continue with OAuth** to approve access on your server.
  </Step>
</Steps>

For OAuth, Superlog registers a client on your server with this redirect URL:

```text theme={null}
https://superlog.sh/api/integrations/custom_mcp/callback
```

On a self-hosted deployment, use your own public URL instead.

## Tool access

Superlog passes every tool the server exposes to the agent. It does not filter them to read-only, so the agent can call write tools if the server has them. Expose only the tools you want agents to use, and write clear tool descriptions so the agent knows when to call them.

Your server receives every call the agent makes. Use its logs to audit what agents did.

Redirects are checked again before they are followed, and authorization is never forwarded to another origin.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.