Skip to main content
BS_128225354-Participant
4-Participant
Oct 15, 2026 8:17 AM UTC
Solved

10.2 MCP Server Unreachable

Hi, 

Before upgrading to 10.2 the MCP server was reachable by default at 

https://mydomain.com/Thingworx/mcp

now after upgrading to 10.2 it returns HTTP status 400 - Bad Request.

Is there anything needed to be done during configuration/installation for 10.2 that could have been missed? Thank you.

smainenteAnswer
16-Pearl
Oct 16, 2026 10:33 AM UTC

Hello,

In 10.2, MCP endpoints are defined using a new entity type called MCP Namespace. Refer to :  Getting Started with Your First MCP Namespace

MCP was a preview feature in 10.1. Tare not migrated during an upgrade to 10.2.0 and are not available after the upgrade. You must recreate these assets by using the MCP Namespace entity.

Please note that the MCP Namespace URL format is now : /Thingworx/mcp/<MY_MCP_NAMESPACE>

An HTTP 400 response is typically returned when the MCP Namespace is missing from the URL. The response body should provide a explicit error message.

I also noticed that the Sample Use Cases section does not clearly mention the updated URL format. I will open a Jira ticket to have the documentation clarified.

View in thread

4 replies

slangleyCommunity Manager
Support
Oct 15, 2026 6:50 PM UTC

Hi ​@BS_12822535.

A case will be needed for this issue as it will require someone to dig into what is going on.  I couldn’t find a support account for you, but if someone else in your organization has one, we can open a case under their credentials.  You will need to private message me the information--I’m happy to open the case.

Regards.

--Sharon

Translate
smainente16-PearlAnswer
16-Pearl
Oct 16, 2026 10:33 AM UTC

Hello,

In 10.2, MCP endpoints are defined using a new entity type called MCP Namespace. Refer to :  Getting Started with Your First MCP Namespace

MCP was a preview feature in 10.1. Tare not migrated during an upgrade to 10.2.0 and are not available after the upgrade. You must recreate these assets by using the MCP Namespace entity.

Please note that the MCP Namespace URL format is now : /Thingworx/mcp/<MY_MCP_NAMESPACE>

An HTTP 400 response is typically returned when the MCP Namespace is missing from the URL. The response body should provide a explicit error message.

I also noticed that the Sample Use Cases section does not clearly mention the updated URL format. I will open a Jira ticket to have the documentation clarified.

Translate
    BS_128225354-ParticipantAuthor
    4-Participant
    Oct 16, 2026 12:16 PM UTC

    Hi, 

    This was the solution. Thank you for your help.

    Translate
    smainente16-Pearl
    16-Pearl
    Oct 16, 2026 12:35 PM UTC

    Thanks you for the update.
    The documentation actually mention that the MCP resource is not migrated:

    MCP

     

    Translate
    Terms & ConditionsAccessibility statement