<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question MCP Server promoted from Dev to Prod still points to the Dev instance URL in Community Central forum</title>
    <link>https://www.servicenow.com/community/community-central-forum/mcp-server-promoted-from-dev-to-prod-still-points-to-the-dev/m-p/3605697#M7995</link>
    <description>&lt;P class=""&gt;&lt;SPAN&gt;Hi everyone,&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;I’m working on a custom MCP server that we created using the &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;MCP Server Console&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt; in our Dev instance. We promoted it to our Prod instance, but after the deployment, the &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;Server URL&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt; in Prod is still pointing to the Dev instance.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;Has anyone come across this behavior before?&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;What is the recommended approach here? Should we use a Fix Script to update the Server URL in Prod, recreate the MCP server directly in Prod using the Console, or is there a specific way to regenerate the URL based on the Prod instance?&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;Would really appreciate any guidance or best practices from anyone who has worked with MCP Server Console deployments across instances.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks in advance!&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 02 Oct 2026 05:17:47 GMT</pubDate>
    <dc:creator>Subhash Velpula</dc:creator>
    <dc:date>2026-10-02T05:17:47Z</dc:date>
    <item>
      <title>MCP Server promoted from Dev to Prod still points to the Dev instance URL</title>
      <link>https://www.servicenow.com/community/community-central-forum/mcp-server-promoted-from-dev-to-prod-still-points-to-the-dev/m-p/3605697#M7995</link>
      <description>&lt;P class=""&gt;&lt;SPAN&gt;Hi everyone,&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;I’m working on a custom MCP server that we created using the &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;MCP Server Console&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt; in our Dev instance. We promoted it to our Prod instance, but after the deployment, the &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;Server URL&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt; in Prod is still pointing to the Dev instance.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;Has anyone come across this behavior before?&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;What is the recommended approach here? Should we use a Fix Script to update the Server URL in Prod, recreate the MCP server directly in Prod using the Console, or is there a specific way to regenerate the URL based on the Prod instance?&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;Would really appreciate any guidance or best practices from anyone who has worked with MCP Server Console deployments across instances.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks in advance!&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 02 Oct 2026 05:17:47 GMT</pubDate>
      <guid>https://www.servicenow.com/community/community-central-forum/mcp-server-promoted-from-dev-to-prod-still-points-to-the-dev/m-p/3605697#M7995</guid>
      <dc:creator>Subhash Velpula</dc:creator>
      <dc:date>2026-10-02T05:17:47Z</dc:date>
    </item>
  </channel>
</rss>

