Loading

HTTP 405 Error When Connecting via Base Path Without /mcp Suffix (MCP Bridge v2)

Publish Date: May 27, 2026
Description
When a new MCP Bridge instance is created using the API Manager (APIM), the default endpoint path behaviour differs depending on the version of MCP Bridge being used:

  • MCP Bridge v1 — Older instances connect and list tools using just the base path defined during setup.
    Assume my base path is /mcpbridge
    Example: http://localhost:8081/mcpbridge 

  • MCP Bridge v2 — Starting from MCP Bridge v2, APIM automatically configures a default /mcp transcoding path appended to the API base path. This change was introduced to ensure compatibility with Agent Fabric / Graph.
    Assume my base path is /bridge
    Example:


Important notes:
  • Existing MCP Bridge v1 instances are not auto-updated — they continue to work with the original base path without any changes.
  • v1 and v2 refer to the MCP Bridge experience/configuration, not the underlying server version. There is no functional difference between the servers other than this new default /mcp transcoding path.
  • The default /mcp transcoding path can be identified in the MCP Bridge instance Policies under MCP Transcoding policy
Resolution

Update your tools list endpoint to include /mcp after the base path when using a newly created MCP Bridge instance (v2)

Assume my base path is /mcpbridge
 http://localhost:8081/bridge/mcp 

Existing MCP Bridge v1 instances are not auto-updated — they continue to work with the original base path without any changes.

Assume my base path is /mcpbridge
http://localhost:8081/mcpbridge 

Knowledge Article Number

005385538

 
Loading
Salesforce Help | Article