Theia API Documentation v1.75.0
    Preparing search index...

    Interface MCPInstallEntryConfig

    Subset of an MCP server's persisted configuration that an install flow may carry: either set by a registry entry or hand-crafted in an install URL. Lives in common so @theia/ai-registry (which resolves registry entries in common) can reference the same canonical shape the browser-side install path writes.

    interface MCPInstallEntryConfig {
        args?: string[];
        command?: string;
        cwd?: string;
        env?: Record<string, string>;
        headers?: Record<string, string>;
        oauth?: MCPOAuthConfig;
        pluginData?: string;
        pluginRoot?: string;
        serverAuthToken?: string;
        serverAuthTokenHeader?: string;
        serverUrl?: string;
    }
    Index

    Properties

    args? command? cwd? env? headers? oauth? pluginData? pluginRoot? serverAuthToken? serverAuthTokenHeader? serverUrl?

    Properties

    args?: string[]
    command?: string
    cwd?: string

    Working directory for the process. Defaults to pluginRoot when that is set.

    env?: Record<string, string>
    headers?: Record<string, string>
    oauth?: MCPOAuthConfig

    OAuth configuration for remote servers. The registry supplies the fixed parts (scopes, authorization server, resource); the confidential-client clientId/clientSecret are collected from the user at install time when the entry advertises them.

    pluginData?: string

    Exported as PLUGIN_DATA. See pluginRoot.

    pluginRoot?: string

    Exported as PLUGIN_ROOT. Its own field rather than an env entry because the MCP edit dialog renders env as a user-editable KEY=VALUE box, and because the reserved variables have to be set after the plugin's env - not expressible once they share one map.

    serverAuthToken?: string
    serverAuthTokenHeader?: string
    serverUrl?: string

    Settings

    Member Visibility

    On This Page

    Properties