v0.0.40

What's Changed

• Fix HTTP backend session initialization to include Mcp-Session-Id headers by @Copilot in #179

Full Changelog: v0.0.38...v0.0.40

v0.0.39

🌟 Release Highlights

This release fixes a critical compatibility issue with HTTP backend MCP servers that require session identification headers.

🐛 Bug Fixes & Improvements

HTTP Backend Session ID Support (#178)

MCP Gateway now properly includes the Mcp-Session-Id header when initializing HTTP backend servers. Previously, HTTP backends that strictly enforce this header requirement would reject initialization requests with "Missing Mcp-Session-Id header" errors, preventing the gateway from starting.

What changed:

• Gateway initialization now creates a context with session ID pattern gateway-init-{serverID} for HTTP backend discovery
• Session IDs are automatically extracted and added as Mcp-Session-Id headers for all HTTP requests
• Fully backward compatible - backends that don't require the header simply ignore it

Impact: This enables MCP Gateway to work seamlessly with strict HTTP MCP servers while maintaining compatibility with all existing backends.

📚 Documentation

Added comprehensive HTTP Backend Session ID documentation covering:

• Problem statement and technical solution
• Session ID flow diagrams for initialization and client requests
• Testing approach and debugging tips

🐳 Docker Image

The Docker image for this release is available at:

docker pull ghcr.io/githubnext/gh-aw-mcpg:v0.0.39
# or
docker pull ghcr.io/githubnext/gh-aw-mcpg:latest

Supported platforms: linux/amd64, linux/arm64

---

Ahoy! This treasure was crafted by 🏴‍☠️ Release

---

What's Changed

• Fix: Add Mcp-Session-Id header for HTTP backend initialization by @Copilot in #178

Full Changelog: v0.0.37...v0.0.39

v0.0.38

What's Changed

• Fix: Add Mcp-Session-Id header for HTTP backend initialization by @Copilot in #178

Full Changelog: v0.0.36...v0.0.38

v0.0.37

🌟 Release Highlights

This release fixes a critical issue with HTTP MCP server authentication by properly propagating session identifiers in requests.

🐛 Bug Fixes

HTTP MCP Server Authentication (#177)

• MCP Gateway now correctly includes the Mcp-Session-Id header when forwarding requests to HTTP MCP servers
• Resolves 400 errors that occurred when HTTP backends (like safeinputs) required session authentication
• Session IDs now flow seamlessly from client requests → gateway context → HTTP backend connections

Technical Details:

• Modified connection layer to accept context.Context and extract session IDs
• Added SessionIDContextKey to avoid circular dependencies between packages
• Updated all call sites in unified and routed modes to pass request context through to the connection layer

This fix ensures that MCP Gateway works correctly with all HTTP-based MCP servers that follow the authentication specification.

🐳 Docker Image

The Docker image for this release is available at:

docker pull ghcr.io/githubnext/gh-aw-mcpg:v0.0.37
# or
docker pull ghcr.io/githubnext/gh-aw-mcpg:latest

Supported platforms: linux/amd64, linux/arm64

---

For complete details, see the full release notes.

Ahoy! This treasure was crafted by 🏴‍☠️ Release

---

What's Changed

• Add Mcp-Session-Id header to HTTP MCP server requests by @Copilot in #177

Full Changelog: v0.0.35...v0.0.37

v0.0.36

What's Changed

• Add Mcp-Session-Id header to HTTP MCP server requests by @Copilot in #177

Full Changelog: v0.0.34...v0.0.36

v0.0.35

🌟 Release Highlights

This release enhances MCP Gateway's observability and compatibility with containerized environments, making it easier to debug and deploy in diverse infrastructure setups.

✨ What's New

🔍 Privacy-Preserving RPC Logger (#173)
MCP Gateway now includes a built-in JSONL logger that captures all JSON-RPC 2.0 messages exchanged between clients and backend MCP servers. This powerful debugging tool helps troubleshoot protocol issues while protecting sensitive data:

• Automatically redacts authentication headers and API keys
• Writes structured logs to mcp-gateway-rpc.log for easy analysis
• Enables protocol-level debugging without compromising security
• Useful for auditing, debugging integration issues, and understanding MCP traffic patterns

Perfect for production debugging and development workflows where you need visibility into MCP protocol exchanges.

🐛 Bug Fixes & Improvements

🐧 Container Detection Compatibility (#175)
Fixed a compatibility issue where MCP Gateway failed to detect host IP addresses in containerized environments using BusyBox (Alpine Linux, minimal containers). The gateway now correctly identifies whether it's running inside a container across different Linux distributions, ensuring proper network configuration and security warnings.

🐳 Docker Image

The Docker image for this release is available at:

docker pull ghcr.io/githubnext/gh-aw-mcpg:v0.0.35
# or
docker pull ghcr.io/githubnext/gh-aw-mcpg:latest

Supported platforms: linux/amd64, linux/arm64

---

Ahoy! This treasure was crafted by 🏴‍☠️ Release

---

What's Changed

• Add privacy-preserving JSONL RPC message logger by @Copilot in #173
• Fix BusyBox grep incompatibility in containerized host IP detection by @Copilot in #175

Full Changelog: v0.0.33...v0.0.35

v0.0.34

What's Changed

• Add privacy-preserving JSONL RPC message logger by @Copilot in #173
• Fix BusyBox grep incompatibility in containerized host IP detection by @Copilot in #175

Full Changelog: v0.0.32...v0.0.34

v0.0.33

🌟 Release Highlights

This release enhances MCP Gateway's containerized deployment capabilities with improved Docker networking support.

✨ What's New

🐳 Enhanced Container Networking - MCP Gateway now automatically configures host.docker.internal DNS resolution when running in containerized environments. This enables seamless communication between the gateway container and other Docker services on the host, particularly useful when MCP backends need to communicate with host-based services or other containers.

This improvement simplifies deployment in containerized environments by eliminating manual DNS configuration and networking workarounds.

🔧 Internal Improvements

• Workflow lock files synchronized with markdown sources for improved CI/CD reliability

🐳 Docker Image

The Docker image for this release is available at:

docker pull ghcr.io/githubnext/gh-aw-mcpg:v0.0.33
# or
docker pull ghcr.io/githubnext/gh-aw-mcpg:latest

Supported platforms: linux/amd64, linux/arm64

---

Ahoy! This treasure was crafted by 🏴‍☠️ Release

---

What's Changed

• Recompile workflow lock files to sync with markdown sources by @Copilot in #169
• Add host.docker.internal DNS resolution for containerized gateway by @Copilot in #174

Full Changelog: v0.0.31...v0.0.33

v0.0.32

What's Changed

• Add daily test improver workflow for Go test quality automation by @Copilot in #166
• Prettify markdown RPC message rendering with proper JSON indentation by @Copilot in #168
• Recompile workflow lock files to sync with markdown sources by @Copilot in #169
• Add host.docker.internal DNS resolution for containerized gateway by @Copilot in #174

Full Changelog: v0.0.29...v0.0.32

v0.0.31

🌟 Release Highlights

This maintenance release improves the debugging experience with enhanced RPC message logging.

⚡ Improvements

Better Debug Logs - RPC messages in debug logs are now formatted with proper JSON indentation instead of compressed single-line format, making it significantly easier to read and debug message flows. Empty payloads (containing only params: null or empty objects) are now omitted entirely for cleaner output.

Example - Before:

**serena**→`tools/list`

~~~
{ "params": null }
~~~

Example - After:

**serena**→`tools/list`

With content:

**serena**→`tools/list`

~~~
{
  "id": 1,
  "params": {
    "arg": "value"
  }
}
~~~

🐳 Docker Image

The Docker image for this release is available at:

docker pull ghcr.io/githubnext/gh-aw-mcpg:v0.0.31
# or
docker pull ghcr.io/githubnext/gh-aw-mcpg:latest

Supported platforms: linux/amd64, linux/arm64

---

For complete details, see the full release notes.

---

Ahoy! This treasure was crafted by 🏴‍☠️ Release

---

What's Changed

• Prettify markdown RPC message rendering with proper JSON indentation by @Copilot in #168

Full Changelog: v0.0.30...v0.0.31