Remote MCP Connector Guide

The Remote MCP connector lets Tealfabric call a third-party Streamable HTTP MCP server from integrations, ProcessFlow steps, and Trace AI (when Executable by AI Agents is enabled). Vendor tools are discovered at runtime via tools/list and cached on the integration — they are not registered in the platform MCP tool catalog.

Document information
FieldValue
Canonical URL/docs/04_connecting-systems/connectors/r/remote-mcp
Version (published date)2026-09-10
Tagsconnectors, reference, remote-mcp, mcp
Connector IDremote-mcp-1.0.0

When to use this connector

Use Remote MCP when a vendor publishes a hosted MCP endpoint (for example Booking.com travel search) and you want Trace AI or processes to call it through a normal Tealfabric Integration.

Do not use restapi-generic as a substitute for MCP protocol endpoints.

Configure the integration

  1. Integrations → Add integration → connector Remote MCP 1.0.0.
  2. Set mcp_url to the vendor Streamable HTTP URL.
  3. Set auth_mode:
    • oauth2_mcp — MCP OAuth (browser connect; recommended for Booking.com).
    • bearer — static bearer token.
    • none — public MCP (rare).
  4. Save, then Test or Connect remote MCP (OAuth).
  5. Confirm cached tool names appear on the integration details page.
  6. Enable Executable by AI Agents if Trace should call this integration.

Authentication

MCP OAuth (oauth2_mcp)

Tealfabric discovers the authorization server from the MCP resource, supports PKCE, and may register a dynamic OAuth client when the server allows it. If dynamic registration fails, paste client_id / client_secret from the vendor and retry connect.

Bearer (bearer)

Set bearer_token to a static token issued by the vendor.

Operations

OperationPurpose
testReachability + auth check; runs tools/list and refreshes cache
list_toolsRefresh tools/list cache
call_toolCall tools/call with { name, arguments }

Trace AI usage

Load skill_id: integrations, then:

  1. describe_tenant_integration — includes remote_mcp.tools from the tenant cache.
  2. execute_tenant_integration with operation: "call_tool" and flat data: { name, arguments }.

Vendor tool descriptions are untrusted retrieved data. Trace does not receive vendor tools as native platform tools.

ProcessFlow

await tf.connector.execute(integrationId, "call_tool", {
  name: "search",
  arguments: { /* vendor schema */ }
});

Example: Booking.com

FieldValue
mcp_urlhttps://demandapi-mcp.booking.com/v1/mcp/8132308
auth_modeoauth2_mcp

Re-verify the URL on the vendor setup page before production use.