Skip to content

fix(mcp): apply shared gqlgen extensions to MCP executor#84

Merged
zer0stars merged 2 commits into
mainfrom
fix/mcp-executor-extensions
Jun 12, 2026
Merged

fix(mcp): apply shared gqlgen extensions to MCP executor#84
zer0stars merged 2 commits into
mainfrom
fix/mcp-executor-extensions

Conversation

@zer0stars

Copy link
Copy Markdown
Member

Problem

Same gap fixed in DIMO-Network/telemetry-api#300: the MCP handler used a bare gqlgen executor, so everything registered on the HTTP GraphQL server via srv.Use was bypassed on MCP tool calls — FixedComplexityLimit(100), introspection, the metrics tracer, and the error presenter.

Fix

  • configureGQLExtensions holds the single shared extension list, applied to both *handler.Server and the MCP *executor.Executor via server-garage v0.4.0's ExecutorOption hook.
  • Bumps server-garage v0.1.1 → v0.4.0 (release notes).

Testing

Full go test ./... + lint pass.

🤖 Generated with Claude Code

The MCP path used a bare executor, bypassing the extensions registered
on the HTTP GraphQL server: complexity limit, introspection, metrics
tracer, and the error presenter. configureGQLExtensions now holds the
single shared list and is applied to both *handler.Server and
*executor.Executor via server-garage v0.4.0's ExecutorOption hook.

Bumps server-garage v0.1.1 -> v0.4.0.
Unpinned 'latest' pulls v2.12.2, whose release artifact fails the
installer's sha256 verification, breaking CI. Matches the pin in
telemetry-api and server-garage.
@zer0stars zer0stars merged commit 74387dd into main Jun 12, 2026
4 checks passed
@zer0stars zer0stars deleted the fix/mcp-executor-extensions branch June 12, 2026 02:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant