Configure MCP Client Accounts

Set up the account type that matches your MCP server's transport protocol and authentication method.

Choosing an account type

MCP Client accounts differ along two dimensions: transport protocol and authentication method. Choose the account type that matches the server you are connecting to.

MCP SSE Account
Use this account to connect to an MCP server that uses the Server-Sent Events (SSE) transport and does not require authentication. SSE is a stateful transport that keeps a persistent connection open for streaming responses. Choose this account type when the server provides an /sse endpoint and allows unauthenticated or header-authenticated access.
MCP SSE OAuth2 Account
Use this account to connect to an MCP server that uses the SSE transport and requires OAuth2 authentication. Choose this account type when the server requires a client ID and secret, issues access tokens via an OAuth2 endpoint, and exposes an /sse endpoint. Supports Authorization Code, Client Credentials, and Password grant types.
MCP Streamable HTTP Account
Use this account to connect to an MCP server that uses the Streamable HTTP transport and does not require authentication. Streamable HTTP is a stateless transport that sends each request independently over HTTP. Choose this account type when the server provides an /mcp endpoint and allows unauthenticated or header-authenticated access.
MCP Streamable HTTP OAuth2 Account
Use this account to connect to an MCP server that uses the Streamable HTTP transport and requires OAuth2 authentication. Choose this account type when the server requires a client ID and secret, issues access tokens via an OAuth2 endpoint, and exposes an /mcp endpoint. Supports Authorization Code, Client Credentials, and Password grant types.

Set up an MCP SSE Account

Use the MCP SSE Account to connect to an MCP server over Server-Sent Events (SSE) without authentication.

  1. In Designer or Manager, open the account creation dialog and select MCP SSE Account.
  2. Enter a unique Label for the account.
  3. Enter the MCP SSE URI — the full URI of the MCP SSE server, including the /sse path.

    Example: https://mcp.deepwiki.com/sse

  4. Optional: In Additional headers, add any Header name and Header value pairs required by the server.
  5. Optional: Set the Timeout in seconds.

    Default: 60

  6. Click Apply.

Set up an MCP SSE OAuth2 Account

Use the MCP SSE OAuth2 Account to connect to an MCP SSE server that requires OAuth2 authentication.

  1. In Designer or Manager, open the account creation dialog and select MCP SSE OAuth2 Account.
  2. Enter a unique Label for the account.
  3. Enter the MCP SSE URI of the MCP SSE server.
  4. Enter the Client ID and Client secret from your OAuth2 provider.
  5. Optional: Select Send Client Data as Basic Auth Header if your OAuth2 provider requires client credentials in the Authorization header.
  6. Optional: Select Trust all certificates to bypass TLS certificate verification for HTTPS requests.
  7. Optional: Select Discover and Register to dynamically register the client with the authorization server using the provided MCP endpoint and parameters.
  8. Enter the OAuth2 Endpoint and OAuth2 Token endpoint URLs from your OAuth2 provider.
  9. Select a Grant Type:
    • Authorization Code: The user authenticates using credentials returned via a redirect URL. The application exchanges the authorization code for an access token.
    • Client Credentials: Obtains an access token using the client ID and secret through the token endpoint URL.
    • Password: Obtains an access token using a username and password. When selected, enter the Username and Password.
  10. Optional: Configure Token endpoint config and Authorization endpoint config to add custom parameters to the token and authorization endpoints.
  11. Click Authorize to complete OAuth2 authorization. The Access token, Refresh token, and Access token expiration fields are populated automatically.
  12. Optional: Set the Timeout in seconds.

    Default: 60

  13. Click Apply.

Set up an MCP Streamable HTTP Account

Use the MCP Streamable HTTP Account to connect to an MCP server over Streamable HTTP without authentication.

  1. In Designer or Manager, open the account creation dialog and select MCP Streamable HTTP Account.
  2. Enter a unique Label for the account.
  3. Enter the MCP Streamable HTTP URI — the full URI of the MCP server, including the /mcp path.

    Example: https://mcp.deepwiki.com/mcp

  4. Optional: In Additional headers, add any Header name and Header value pairs required by the server.
  5. Optional: Set the Timeout in seconds.

    Default: 60

  6. Click Apply.

Set up an MCP Streamable HTTP OAuth2 Account

Use the MCP Streamable HTTP OAuth2 Account to connect to an MCP Streamable HTTP server that requires OAuth2 authentication.

  1. In Designer or Manager, open the account creation dialog and select MCP Streamable HTTP OAuth2 Account.
  2. Enter a unique Label for the account.
  3. Enter the MCP Streamable HTTP URI of the MCP server.
  4. Enter the Client ID and Client secret from your OAuth2 provider.
  5. Optional: Select Send Client Data as Basic Auth Header if your OAuth2 provider requires client credentials in the Authorization header.
  6. Optional: Select Trust all certificates to bypass TLS certificate verification for HTTPS requests.
  7. Optional: Select Discover and Register to dynamically register the client with the authorization server using the provided MCP endpoint and parameters.
  8. Enter the OAuth2 Endpoint and OAuth2 Token endpoint URLs from your OAuth2 provider.
  9. Select a Grant Type:
    • Authorization Code: The user authenticates using credentials returned via a redirect URL. The application exchanges the authorization code for an access token.
    • Client Credentials: Obtains an access token using the client ID and secret through the token endpoint URL.
    • Password: Obtains an access token using a username and password. When selected, enter the Username and Password.
  10. Optional: Configure Token endpoint config and Authorization endpoint config to add custom parameters to the token and authorization endpoints.
  11. Click Authorize to complete OAuth2 authorization. The Access token, Refresh token, and Access token expiration fields are populated automatically.
  12. Optional: Set the Timeout in seconds.

    Default: 60

  13. Click Apply.