Powered by Zoomin Software. For more details please contactZoomin

Progress Data Platform Help

Connect MCP clients to Data Platform

  • Last Updated: November 19, 2026
  • 3 minute read
    • Documentation

Connect external AI agents and applications to project data through the Model Context Protocol (MCP). Each project has an MCP URL that you can add to an MCP-compatible client.

To connect an MCP client to Data Platform:

  1. Get the project MCP URL.
  2. Add the connection to your client.
  3. Authenticate.

Before you begin

  • Use a client that supports remote MCP servers over Streamable HTTP.
  • The user that you sign in as must have the Platform User role and at least Reader access to the project. Reader access is sufficient to read project data. Tools that change data or run pipelines require Writer access. See Share access.
  • If you use an API key, make sure it has access to the project. API keys receive the Platform User role automatically when they are granted project access. See Manage API keys.
  • To copy the MCP URL from the project settings, you need the Platform Manager role. Otherwise, ask a project member who has this role to share the URL.

1. Get the project MCP URL

To get the MCP URL:

  1. Open the project.
  2. At the top of the page, click Project options, and then select Settings. The Project Settings window opens.
  3. Select Advanced.
  4. In the MCP section, click Copy.

The project MCP URL is copied to your clipboard. It is specific to the project and its zone.

2. Add the connection to your client

To add the Data Platform MCP server:

  1. In your MCP client, add a remote MCP server.
  2. Enter the project MCP URL.
  3. If the client asks for a transport, select Streamable HTTP.
  4. Save or connect to the server.

The names and locations of these settings vary by client. For client-specific instructions, see the documentation for your MCP client.

3. Authenticate

Choose an authentication method supported by your client:

  • OAuth: Sign in through the browser when the client prompts you. The client uses your identity and project access.
  • API key: Use an API key for automated connections. Enter it in the client's secure credential field, following the client's instructions for API-key authentication. Do not put the key in the MCP URL or in a shared configuration file.

For details about authentication and access, see Authentication and Share access.

When the connection succeeds, the client can discover and use the tools that your roles allow.

Troubleshooting

The following table describes common issues you might encounter when connecting an MCP client to Data Platform and potential solutions.

Issue What to do
The client cannot connect to the server. Confirm that you copied the URL from the correct project's Project Settings window under Advanced > MCP, that the client supports remote MCP over Streamable HTTP, and that your network allows HTTPS connections to the project's zone.
The client reports an authentication error. Sign in again with OAuth, or check that the API key is valid and configured using the client's supported authentication method.
The client connects but cannot access project data or tools. Confirm that the signed-in user has the Platform User role, and that the user or API key has access to the project. Ask an account owner to assign platform roles. For project access, see Manage project access for users or Grant an API key access to a project for API keys.
Alert