You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Title:
Add native elicitation/create support to Spring AI MCP Server for MCP 2025-06-18 spec
Description:
The MCP specification (2025-06-18) introduces the Elicitation feature, which allows an MCP server to send an elicitation/create request to the connected client with a flat JSON Schema. The client renders a form in the UI and returns structured user input (accept, decline, or cancel).
A tool could call this mid-execution, prompting the client to display a text field and submit button.
Current status in Spring AI:
The Spring AI MCP Client Boot Starter documentation (link to client docs section) references elicitation in the context of client capabilities.
The Spring AI MCP Server Boot Starter does not currently expose a native, first-class API for sending elicitation/create requests.
Implementing elicitation today requires manually retrieving McpSyncServerExchange from ToolContext and issuing exchange.request("elicitation/create", …) with a raw schema map.
Feature request:
Please add a native API to Spring AI MCP Server Boot Starter to support Elicitation end-to-end:
Capability detection – At tool runtime, automatically detect if the connected client supports elicitation (advertised in initialize).
First-class server API – Provide a simple, type-safe way to send elicitation/create with a provided flat JSON Schema and optional progress token.
Response handling – Return a structured result object encapsulating accept / decline / cancel and typed content.
Optional annotation/config support – Allow tool methods to declare elicitation prompts directly in @Tool metadata, so Spring can handle sending and parsing the request automatically.
Benefits:
Keeps elicitation fully within Spring AI idioms (no low-level JSON-RPC calls).
Improves developer productivity for interactive workflows.
Enables richer integrations with MCP clients that can render structured forms.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Title:
Add native
elicitation/createsupport to Spring AI MCP Server for MCP 2025-06-18 specDescription:
The MCP specification (2025-06-18) introduces the Elicitation feature, which allows an MCP server to send an
elicitation/createrequest to the connected client with a flat JSON Schema. The client renders a form in the UI and returns structured user input (accept,decline, orcancel).This enables scenarios like:
{ "type": "object", "properties": { "name": { "type": "string", "title": "Your name", "minLength": 1 } }, "required": ["name"] }A tool could call this mid-execution, prompting the client to display a text field and submit button.
Current status in Spring AI:
elicitationin the context of client capabilities.elicitation/createrequests.McpSyncServerExchangefromToolContextand issuingexchange.request("elicitation/create", …)with a raw schema map.Feature request:
Please add a native API to Spring AI MCP Server Boot Starter to support Elicitation end-to-end:
initialize).elicitation/createwith a provided flat JSON Schema and optional progress token.accept/decline/canceland typed content.@Toolmetadata, so Spring can handle sending and parsing the request automatically.Benefits:
References:
Beta Was this translation helpful? Give feedback.
All reactions