---
title: Sharing MCP server URLs (early access)
description: Share the PingOne Remote MCP Server configuration URL across environments and administrators using the home environment ID.
component: build-with-ai
page_id: build-with-ai:pingone-mcp-server:p1-sharing-mcp-configuration
canonical_url: https://developer.pingidentity.com/build-with-ai/pingone-mcp-server/p1-sharing-mcp-configuration.html
llms_txt: https://developer.pingidentity.com/build-with-ai/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: 2026-08-28
keywords: ["MCP", "AI", "PingOne", "Model Context Protocol", "identity orchestration", "cross-environment administration"]
section_ids:
  before-you-begin: Before you begin
  mcp-server-url-structure: MCP server URL structure
  cross-environment-url-sharing: Cross-environment URL sharing
  default-behavior: Default behavior
  sharing-across-environments: Sharing across environments
---

# Sharing MCP server URLs (early access)

PingOne uses a cross-environment administration model, which lets administrators manage environments other than their own home environment.

## Before you begin

To view and copy the MCP server configuration URL in the PingOne admin console, your administrator role must include the `adminMcp:read:settings` permission.

## MCP server URL structure

The MCP server URL uses the following format:

```none
https://mcp.pingone.region/admin/envId/mcp
```

## Cross-environment URL sharing

|   |                                                                                                                                   |
| - | --------------------------------------------------------------------------------------------------------------------------------- |
|   | The `/envId` path parameter must be the home environment ID of the administrator who authenticates the request to the MCP server. |

### Default behavior

When you view the URL in the PingOne admin console, PingOne automatically populates `/envId` with your own home environment ID. Learn more about home environments in [Best Practices for Managing PingOne Admin Users](https://support.pingidentity.com/s/article/Best-Practices-for-Managing-PingOne-Admin-Users) in the Ping Identity Support knowledgebase.

### Sharing across environments

If you share this URL with an administrator whose identity resides in a different home environment, they must replace `/envId` with their own home environment ID before they connect their MCP client. Otherwise, their MCP client can't authenticate successfully to the PingOne Remote MCP Server.