Skip to content

Conversation

@caseychow-oai
Copy link

@caseychow-oai caseychow-oai commented Feb 11, 2026

Summary

Declare MCP-compliant client elicitation capabilities by explicitly advertising form/url support.

Type of Change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Documentation update
  • Refactoring (no functional changes)
  • Test updates
  • Build/CI improvements

Changes Made

  • Updated client initialization capabilities in client/src/lib/hooks/useConnection.ts:
    • elicitation is now declared as:
      • form: {}
      • url: {}
  • Updated client/src/lib/hooks/__tests__/useConnection.test.tsx to validate the explicit elicitation.form and elicitation.url declaration.

Related Issues

N/A

Testing

  • Tested in UI mode
  • Tested in CLI mode
  • Tested with STDIO transport
  • Tested with SSE transport
  • Tested with Streamable HTTP transport
  • Added/updated automated tests
  • Manual testing performed

Test Results and/or Instructions

  • npm install succeeded after network fix.
  • Build completed successfully.
  • Automated test expectation updated for explicit elicitation capability shape.

Checklist

  • Code follows the style guidelines (ran npm run prettier-fix)
  • Self-review completed
  • Code is commented where necessary
  • Documentation updated (README, comments, etc.)

Breaking Changes

None.

Additional Context

This aligns client capability declaration with MCP spec shape: elicitation: { form: {}, url: {} }.

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