[MCP Connector] MCP Connectors for streamable HTTP

[rithin-pullela-aws]

Description

Similar to SSE connectors people can now create streamable HTTP connectors and use them in agents

Only change is the connector creation:

{
  "name": "My MCP Connector",
  "description": "The connector to MCP server",
  "version": 1,
  "protocol": "mcp_streamable_http",
  "credential": {
    "mcp_server_key": "testmcp"
  },
  "parameters":{
    "endpoint": "/mcp/"
  },
  "url": "http://localhost:9900",
  "headers": {
    "Authorization": "Bearer ${credential.mcp_server_key}"
  }
}

Related Issues

Resolves #[Issue number to be closed when this PR is merged]

Check List

• New functionality includes testing.
• New functionality has been documented.
• API changes companion pull request created.
• Commits are signed per the DCO using --signoff.
• Public documentation issue/PR created.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[rithin-pullela-aws]

I see the example used endpoint and url

  "parameters":{
    "endpoint": "/mcp/"
  },
  "url": "http://localhost:9900",

Why not just use url http://localhost:9900/mcp

@ylwu-amzn. the MCP sdk resolves the URL to the most basic string.

For example when even when we provide the URL as http://localhost:9900/mcp/xyz/anc it will internally convert it to http://localhost:9900/mcp and it uses the endpoint variable to talk to the server.
Hence we need both URL and endpoint