---
title: Deploying an MCP server
description: "Deploy an PingOne Authorize MCP server to publish updated configuration and authorization policies to the MCP server's system-owned decision endpoint."
component: pingone
page_id: pingone:authorization_using_pingone_authorize:p1az_deploying_mcp_servers
canonical_url: https://docs.pingidentity.com/pingone/authorization_using_pingone_authorize/p1az_deploying_mcp_servers.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-26T21:53:32Z
section_ids:
  steps: Steps
---

# Deploying an MCP server

Deploy an MCP server each time you make configuration changes, such as updating a setting or updating custom policies.

Each MCP server has a system-owned [decision endpoint](p1az_decision_endpoints.html) that provides an environment for deploying the MCP server and its authorization policies. The decision endpoint is created when you deploy the MCP server for the first time, and it has the same name as the MCP server.

Deploying the MCP server also deploys the latest version of the MCP server module's policy tree. This publishes custom policies that target the MCP server.

|   |                                                                                                            |
| - | ---------------------------------------------------------------------------------------------------------- |
|   | Don't use **Version History** to publish policies that target MCP servers. Instead, deploy the MCP server. |

## Steps

1. Go to **Authorization > MCP Servers** and select the MCP server that you want to deploy.

   If the MCP server has already been deployed, a timestamp at the bottom of the page provides information about the last successful deployment.

2. Click **Deploy**.