Custom Remote MCP

Custom integrations are useful when your organization already operates an MCP server that is not part of Oblive’s reviewed catalog.

Supported Contract

Custom MCP v1 requires:

• Streamable HTTP transport;
• a public HTTPS URL;
• no user information or URL fragment;
• no custom port;
• no local, private, link-local, or cloud-metadata address; and
• no redirect during discovery.

Authentication can be:

• none;
• a Bearer API key; or
• one named static header.

Commands, package names, STDIO configuration, environment definitions, and runtime downloads are not accepted from organization configuration.

Add the Server

1. Open Integrations and choose to add a custom server.
2. Enter a stable name and public HTTPS endpoint.
3. Select the authentication method and provide the write-only credential if required.
4. Discover tools.
5. Review tool names and descriptions.
6. Choose read-only or full access.
7. Select only the tools the organization intends to expose.
8. Save and run a bounded read to verify the connection.

Access Rules

Read-only mode exposes only tools whose annotations explicitly mark them read-only. A missing or false annotation fails closed. Full access can expose selected consequential tools, but those tools still use the same task, approval, receipt, and reconciliation lifecycle as managed providers.

When to Use a Managed Integration Instead

Use a reviewed managed integration when the provider is broadly useful, needs curated setup guidance, requires a fixed tool allowlist, or should receive deterministic profile grants and an agent skill.