Choose an MCP Server Transport

Choose a local command for an MCP server installed on the same machine, or a remote URL for a server reached over the network.

Local server

A local MCP server runs as a child process and communicates through standard input and output (stdio). Configure the command, arguments, and required environment values.

Use a local server when its tools need local executables or project resources. Review the command before enabling it because the process runs with the access available to the Reasoning environment.

Remote server

A remote MCP server is configured with an HTTP or HTTPS URL. Reasoning supports Streamable HTTP and compatibility with SSE endpoints. A URL ending in /sse is treated as an SSE endpoint; other remote connections try the supported HTTP transport and compatibility fallback.

Remote servers can require OAuth authentication or client registration. Use the actions shown in MCP Servers to complete the connection instead of placing tokens in the URL.

Choose the scope

Transport and scope are separate choices. A local or remote server can still belong to project configuration or global configuration.

After configuring the server, follow Use MCP in a Session to verify the connection and permission flow.