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. Choose Ask before writes or Autonomous. Custom tools require a write-capable permission mode because remote annotations are not trusted as an authorization boundary.
5. Connect and discover the bounded tool inventory.
6. Review tool names and descriptions. All currently eligible tools start selected; narrow the explicit snapshot to only the tools the organization intends to expose.
7. Save and run a bounded task through the normal action policy to verify the connection.

Access Rules

Custom remote annotations are never trusted to reduce risk. Read-only mode therefore exposes no custom tools. Ask before writes or Autonomous can expose selected custom tools, but every call is consequential and uses the same task, receipt, and reconciliation lifecycle as managed providers. Ask before writes stages each call for human approval; Autonomous may execute it directly.

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.