Support Streamable HTTP transport for remote MCP clients

[philmilroy118118]

Use case

We want to connect the official Octopus Deploy MCP server to AWS DevOps Agent.

AWS DevOps Agent only supports remote MCP servers using Streamable HTTP. It cannot launch or communicate with stdio-only MCP processes.

The current Octopus MCP server appears to support only stdio transport, which works well for local clients such as Claude Code, Codex, Cursor and MCP Inspector, but prevents use with hosted agent platforms.

Requested capability

Please add support for Streamable HTTP transport, ideally alongside the existing stdio transport.

A possible invocation might be:

octopus-mcp-server \
  --transport streamable-http \
  --host 0.0.0.0 \
  --port 8080 \
  --read-only

Deployment scenario

Our intended architecture is:

AWS DevOps Agent
→ authenticated Streamable HTTP MCP endpoint
→ Octopus MCP server running in ECS/Fargate
→ Octopus Deploy API

The service would be long-running and deployed as a container.

Authentication

AWS DevOps Agent supports MCP endpoint authentication using:

OAuth 2.0 client credentials
OAuth 2.0 3LO
API key/token
AWS SigV4

Native authentication support would be useful, although transport support alone would allow authentication to be handled by an ingress proxy or gateway.

Why this would be useful

This would make the official server usable with hosted and enterprise MCP clients, rather than only clients capable of launching local stdio processes.

It would also avoid users needing to maintain third-party stdio-to-HTTP proxies or forks of the official server.

Local testing

For ref, I have already:

• tested the official container locally;
• successfully connected through MCP Inspector;
• successfully called list_spaces;
• confirmed the only blocker is the transport mismatch.