Databricks SDK for JavaScript
    Preparing search index...

    Operational configuration for an MCP service. Groups the source reference, tool selectors, and rate limits -- the fields that configure how the MCP service behaves at invocation time.

    interface McpServiceConfig {
        includeToolSelectors?: string[];
        rateLimits?: RateLimit[];
        source?: {
            $case: "sourceConnection";
            sourceConnection: McpServiceConfig_SourceConnection;
        };
    }
    Index

    Properties

    includeToolSelectors?: string[]

    Tool names or prefix patterns to expose from the MCP server. Use exact tool names or prefix patterns such as read_*. An empty list exposes all tools. At most 1,024 selectors are allowed, and each selector can contain at most 256 characters.

    rateLimits?: RateLimit[]

    Rate limits for tool invocations. Supported scopes are user, group, service principal, the service as a whole, and each user by default. Request and token limits are supported. Empty when no rate limit is configured.

    source?: {
        $case: "sourceConnection";
        sourceConnection: McpServiceConfig_SourceConnection;
    }

    Polymorphic reference to where the MCP server lives. MCP_SERVICE is a single-kind securable (MCP_SERVICE_STANDARD) with two source variants: source_connection (a UC Connection FQN) and internal (a -hosted MCP server). (-- Future MANAGED variants (if introduced) would slot additional oneof entries here. --)

    JSON shape: the active oneof variant appears as a sibling field on config (proto JSON does not nest the oneof container name). E.g.: { "config": { "source_connection": {"name": "connections/main.default.gh"}, "include_tool_selectors": ["read_*"], ... } } { "config": { "internal": {"server": "sandbox"}, ... } } Future variants slot in the same way: {"config": {"app": {...}, ...}}, {"config": {"genie": {...}, ...}}, etc. (-- The oneof shape lets future kinds add type-specific reference shapes without a wire-format bump. --)

    Type Declaration