Connecting to an MCP Server

Learn how to connect to an MCP Server.

To establish an authenticated connection from an MCP Client to an MCP Server, you need to ensure the following:

Get the MCP Server URL

1. In the OCI console, for the selected MCP Server Details page, copy the Server URL.

2. Add this Server URL into your MCP Client when adding the remote server.

   

Ensure You Are Assigned an Application Role

To access the MCP Server, you must be assigned at least one application role. For more information about application roles, see Role-Based Access Control for MCP Server Tools and Reports.

The assigned application roles are included in the authentication token and are used by the MCP Server to authorize access to Tools and SQL Reports.

Choose an Authentication Method that the MCP Client Supports

• OAuth 2.0

  Use this option if:

  • Your MCP client supports OAuth, or
  • Your MCP client only supports local stdio transport. Use a proxy such as mcp-remote to handle OAuth and remote HTTP communication.

  To connect to an MCP server using OAuth:

  1. In your MCP client, select OAuth authentication.
  2. Sign in when prompted to obtain an OAuth token.

  For more information, see OAuth 2.0 and OpenID Connect.

• Personal Access Token

  Use this option if your MCP client supports MCP over HTTP, but does not support OAuth. For more information about Personal Access Tokens, see Generating an Access Token.

  You need:

  • A domain.
  • A user within that domain.
  • A Personal Access Token created for that user.

  The connect to an MCP server using a Personal Access Token, follow these general steps:

  1. Confirm your domain and username.
  2. Create or obtain a Personal Access Token.
  3. In the MCP client, choose Personal Access Token authentication. Enter the required details and add the Personal Access Token.

  See Tutorial: Set Up a Database Tools MCP Server and Integrate with an MCP Client for a step-by-step process that includes both authentication methods.