-
Notifications
You must be signed in to change notification settings - Fork 314
Open
Description
Summary
MCP Gateway v0.2.4: tools/list returns HTTP 400 for Atlassian MCP HTTP.
The issue #19652 was closed but the problem still persists.
Environment
| Component | Version |
|---|---|
| gh-aw | v0.63.1 |
| MCP Gateway | v0.2.4 |
| Backend | Atlassian MCP Server (Streamable HTTP transport) |
| Endpoint | https://mcp.atlassian.com/v1/mcp |
Steps to Reproduce
- Configure an HTTP-based MCP backend (Atlassian MCP Server):
mcp-servers: atlassian: url: https://mcp.atlassian.com/v1/mcp headers: Authorization: Basic ${{ secrets.ATLASSIAN_BASIC_AUTH_BASE64 }} allowed: ["*"]
Run a workflow that uses the Atlassian MCP backend
Attempting connection (timeout: 10s)...
✓ atlassian: connected
⏱️ TIMING: Server check for atlassian took 80ms
[2026-03-25T12:21:00Z] [DEBUG] [backend] GetOrLaunch called for server: atlassian
[2026-03-25T12:21:00Z] [INFO] [backend] Configuring HTTP MCP backend: atlassian, url=https://mcp.atlassian.com/v1/mcp
[2026-03-25T12:21:00Z] [INFO] [backend] Successfully configured HTTP MCP backend: atlassian
[2026-03-25T12:21:01Z] [WARN] [backend] Failed to register tools from atlassian (took 538.570177ms): backend error listing tools: code=-32603, message=HTTP 400: Bad Request
Expected Behavior
tools/list should succeed and return the available tools from the Atlassian MCP server.
Actual Behavior
tools/list fails with HTTP 400: Bad Request
Reactions are currently unavailable
Metadata
Metadata
Assignees
Type
Fields
Give feedbackNo fields configured for issues without a type.