Enhanced OAS server URL path handling for MCP in Apigee

Enhanced OAS server URL path handling for MCP in Apigee

With this feature enhancement, your OpenAPI specification (OAS) configurations behave exactly as defined in the OAS standard, automatically combining the server.url base path value with individual operation paths.

For example, a server URL ofhttps://example.com/api/v1 paired with a path of /users will now correctly route to https://example.com/api/v1/users without additional manual intervention.

If you previously prepended base paths to your OAS paths entries, remove the path segment from your servers.url field to prevent duplication. For example, change https://example.com/api/v1 to https://example.com.

For more information, see Create an OpenAPI 3.0 specification.