Skip to content

Add explicit type: http to MCP server config#73

Merged
theletterf merged 1 commit intomainfrom
explicit-mcp-type
Apr 9, 2026
Merged

Add explicit type: http to MCP server config#73
theletterf merged 1 commit intomainfrom
explicit-mcp-type

Conversation

@theletterf
Copy link
Copy Markdown
Member

Summary

The gh-aw gateway defaults MCP server transport to stdio. Adding type: http explicitly to avoid initialization failures for the remote Elastic Docs MCP server.

The gateway health check was showing "elastic-docs":{"status":"error","uptime":0} when called cross-repo, possibly because the transport type wasn't being inferred from the url field.

Test plan

  • After release: trigger issue-triage from docs-content, verify MCP server status is running in gateway health check

🤖 Generated with Claude Code

The gh-aw gateway defaults to stdio transport. Be explicit about
HTTP to avoid initialization failures for remote MCP servers.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@theletterf theletterf self-assigned this Apr 9, 2026
@theletterf theletterf closed this Apr 9, 2026
@theletterf theletterf reopened this Apr 9, 2026
@theletterf theletterf merged commit 673607f into main Apr 9, 2026
7 checks passed
@theletterf theletterf deleted the explicit-mcp-type branch April 9, 2026 13:10
theletterf added a commit that referenced this pull request Apr 13, 2026
Resolve conflicts from PR #73 (explicit MCP type) by recompiling
lock files with the updated sources.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant