Skip to content

Add notifications/elicitation/complete to MCP parser#4157

Merged
JAORMX merged 1 commit intomainfrom
jaosorior/add-elicitation-complete-notification
Mar 16, 2026
Merged

Add notifications/elicitation/complete to MCP parser#4157
JAORMX merged 1 commit intomainfrom
jaosorior/add-elicitation-complete-notification

Conversation

@JAORMX
Copy link
Collaborator

@JAORMX JAORMX commented Mar 16, 2026

Summary

  • The MCP 2025-11-25 spec defines notifications/elicitation/complete as a server-to-client notification sent when an out-of-band URL-mode elicitation completes. This was the only spec-defined method not yet handled by the parser (30 of 31 covered).
  • Adds a handler that extracts elicitationId as the resource identifier, plus tests for the middleware round-trip and extraction logic.

Type of change

  • New feature

Test plan

  • Unit tests (task test)
  • Linting (task lint-fix)

Generated with Claude Code

The MCP 2025-11-25 spec defines notifications/elicitation/complete as a
server-to-client notification sent when an out-of-band URL-mode
elicitation completes. This was the only spec method not yet handled
by the parser.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@github-actions github-actions bot added the size/XS Extra small PR: < 100 lines changed label Mar 16, 2026
@codecov
Copy link

codecov bot commented Mar 16, 2026

Codecov Report

❌ Patch coverage is 50.00000% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 68.86%. Comparing base (ba38a12) to head (bd4503e).
⚠️ Report is 16 commits behind head on main.

Files with missing lines Patch % Lines
pkg/mcp/parser.go 50.00% 0 Missing and 2 partials ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4157      +/-   ##
==========================================
- Coverage   68.88%   68.86%   -0.03%     
==========================================
  Files         461      464       +3     
  Lines       46562    46729     +167     
==========================================
+ Hits        32075    32179     +104     
- Misses      11987    11997      +10     
- Partials     2500     2553      +53     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Contributor

@jhrozek jhrozek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM — spec-compliant, well-tested, completes coverage of all 31 MCP 2025-11-25 methods.

While reviewing, noticed a pre-existing issue: progress/update in the methodHandlers map is not a valid MCP spec method (only notifications/progress is). Filed #4170 to track cleanup.

@JAORMX JAORMX merged commit b4acadf into main Mar 16, 2026
70 of 71 checks passed
@JAORMX JAORMX deleted the jaosorior/add-elicitation-complete-notification branch March 16, 2026 18:17
aron-muon pushed a commit to aron-muon/toolhive that referenced this pull request Mar 16, 2026
The MCP 2025-11-25 spec defines notifications/elicitation/complete as a
server-to-client notification sent when an out-of-band URL-mode
elicitation completes. This was the only spec method not yet handled
by the parser.

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

size/XS Extra small PR: < 100 lines changed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants