Skip to content

fix: Align ElicitResult action naming with specification#2316

Closed
goingforstudying-ctrl wants to merge 3 commits intomodelcontextprotocol:mainfrom
goingforstudying-ctrl:fix/elicitation-action-naming
Closed

fix: Align ElicitResult action naming with specification#2316
goingforstudying-ctrl wants to merge 3 commits intomodelcontextprotocol:mainfrom
goingforstudying-ctrl:fix/elicitation-action-naming

Conversation

@goingforstudying-ctrl
Copy link

Summary

Fix inconsistent naming between Python SDK and MCP specification for Elicitation actions.

Problem

The MCP specification defines three actions for Elicitation:

  • accept
  • reject
  • cancel

However, the Python SDK was using "decline" instead of "reject", causing inconsistency.

Solution

Changed the action literal from "decline" to "reject" in ElicitResult type definition to align with the specification.

Impact

This is a breaking change for any code using the "decline" action. Users will need to update their code to use "reject" instead.

Fixes #1056

PR-Contributor and others added 3 commits March 19, 2026 21:23
Add optional protocol_version parameter to ClientSession.__init__() to allow
callers to override the default LATEST_PROTOCOL_VERSION when connecting to
servers that require a specific protocol version.

Fixes modelcontextprotocol#2307
Change action value from "decline" to "reject" to match the MCP specification.

The specification defines three actions for Elicitation:
- accept
- reject
- cancel

But the Python SDK was using "decline" instead of "reject". This fixes
the inconsistency between the SDK and the specification.

Fixes modelcontextprotocol#1056
@maxisbey maxisbey closed this Mar 20, 2026
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.

inconsistent actions between python sdk and specification for Elicitation

2 participants