---
title: Editing an MCP server
description: Edit a PingOne Authorize MCP server.
component: pingone
page_id: pingone:authorization_using_pingone_authorize:p1az_edit_mcp_server
canonical_url: https://docs.pingidentity.com/pingone/authorization_using_pingone_authorize/p1az_edit_mcp_server.html
llms_txt: https://docs.pingidentity.com/pingone/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: 2026-10-29T02:59:50Z
section_ids:
  steps: Steps
---

# Editing an MCP server

You can edit Model Context Protocol (MCP) server settings, such as the name, RPC endpoint URLs, and protected resource metadata (PRM) URL. You can also edit the PingOne resource associated with the MCP server if PingOne SSO is the token source.

## Steps

1. Go to **Authorization > MCP Servers**, click the **More Options** icon ([icon: ellipsis-vertical, set=fa]) next to the MCP server you want to edit, and select **Edit**.

2. Update any of the following settings:

   1. (Optional) Change the MCP server **Name**.

   2. (Optional) Add to or change the **RPC Endpoint URLs**.

   3. (Optional) Change the **Protected Resource Metadata Discovery URL**.

      |   |                                                                                                                                                                                                                                                                                 |
      | - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
      |   | If the PRM URL is currently a relative URL, and the MCP server has multiple RPC endpoint URLs, you can't change it to an absolute URL. Similarly, if the PRM URL is an absolute URL, you can't add more RPC endpoint URLs without first changing the PRM URL to a relative one. |

   4. (Optional) To change the PingOne resource associated with the MCP server, select a resource from the list, or select the option to **Create a new resource**.

      The resource is managed by the MCP server and there are restrictions against deleting the resource while it's associated with the MCP server. Resources created automatically have the same name as the MCP server. Learn more about resources in [MCP servers](p1az_mcp_servers.html).

   5. Click **Save**.

3. To edit the MCP server's authorized scopes:

   |   |                                                                                                                                                                                 |
   | - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   |   | If user directory services and access token validation are managed externally, use your external identity provider (IdP), such as PingFederate, to configure authorized scopes. |

   1. Under **PingOne Resource**, click the resource name.

   2. In **Applications > Resources**, click the **Scopes** tab.

   3. (Optional) Change a scope **Name** or **Description**.

   4. (Optional) To add a scope:

      1. Click **+ Add Scope**.

      2. Enter a **Name** and **Description**.

      3. Select the **Enabled Mapped Attributes** checkbox to map attributes to the scope.

         Learn more in [Editing a resource](../applications/p1_editresource.html).

      4. Click **Save**.

   5. (Optional) To edit a scope:

      1. Click the **[icon: pencil, set=fa]**next to the scope.

      2. Change the **Name** or **Description**.

      3. Clear the **Enabled Mapped Attributes** checkbox to remove attribute mappings from the scope, or select attributes in the list to add attribute mappings.

      4. Click **Save**.

   6. (Optional) To remove a scope, click the **Delete** next to the scope, select the checkbox to confirm the deletion, and then click **Delete**.

4. To edit custom policies for the MCP server:

   1. Go to **Authorization > Policies**, and select the MCP server's module in the **Module** list.

   2. In the policy tree, select the **Custom** policy set nested under the MCP server's **Inbound Request** policy set.

   3. Update the policy, and then click **Save changes**.

   4. Go to **Authorization > MCP Servers** and select the MCP server.

   5. Click **Deploy**.