> ## Documentation Index
> Fetch the complete documentation index at: https://developer.watson-orchestrate.ibm.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configuring the watsonx Orchestrate ADK MCP Server

## Transport Mode

The watsonx Orchestrate ADK MCP Server supports three transport modes: [STDIO](https://modelcontextprotocol.io/specification/2025-06-18/basic/transports#stdio), [SSE](https://modelcontextprotocol.io/specification/2024-11-05/basic/transports#http-with-sse), and [HTTP STREAMABLE](https://modelcontextprotocol.io/specification/2025-06-18/basic/transports#streamable-http).

The server includes native support for all three transport types. You choose the transport mode by setting the `WXO_MCP_TRANSPORT` environment variable to `stdio`, `sse`, or `http`.

**Example:**

<Tabs>
  <Tab title="STDIO">
    ```txt .env theme={null}
    WXO_MCP_TRANSPORT=stdio
    ```
  </Tab>

  <Tab title="SSE">
    ```txt .env theme={null}
    WXO_MCP_TRANSPORT=sse
    ```
  </Tab>

  <Tab title="HTTP STREAMABLE">
    ```txt .env theme={null}
    WXO_MCP_TRANSPORT=http
    ```
  </Tab>
</Tabs>

By default, the server runs using STDIO. This works only for locally running servers. For remote connections, HTTP STREAMABLE is the preferred method. Consider how and where you want the server to run when selecting a transport type.

## Network Settings

When using SSE or HTTP STREAMABLE, the server runs as an HTTP web server on a specific host and port. By default, the host is `127.0.0.1` and the port is `8080`.

You configure both options using the `WXO_MCP_HOST` and `WXO_MCP_PORT` environment variables.

## File Access

Many features in the watsonx Orchestrate ADK rely on reading and writing files, such as importing or exporting resources. By default, the watsonx Orchestrate MCP Server blocks tools from accessing the file system where the server runs, for security reasons.

To allow access, set a root working directory using the `WXO_MCP_WORKING_DIRECTORY` environment variable. This enables tools in the MCP Server to read and write files, as long as they stay within that directory or its subdirectories.

**Example:**

```txt .env theme={null}
WXO_MCP_WORKING_DIRECTORY=<file_path>
```