[Feature Request]: MCP Elicitation (v2025-06-18)

[CalebBartleMAA]

🧭 Type of Feature

Please select the most appropriate category:

• Enhancement to existing functionality
• New feature or capability
• New MCP-compliant server
• New component or integration
• Developer tooling or test improvement
• Packaging, automation and deployment (ex: pypi, docker, quay.io, kubernetes, terraform)
• Other (please describe below)

🧭 Epic

Title: MCP Elicitation Server (v2025-06-18)
Goal: Implement a new MCP-compliant server supporting the Elicitation protocol as defined in the 2025-06-18 specification, enabling advanced client-driven elicitation workflows.
Why now: The latest MCP Elicitation protocol introduces new capabilities for structured, interactive information gathering and workflow automation. Supporting this will enable richer integrations and more flexible client-server interactions for all MCP users.

---

🙋♂️ User Story 1

As a: Solution architect
I want: to deploy an MCP Elicitation server compliant with the 2025-06-18 spec
So that: my clients can leverage advanced elicitation workflows and structured data collection

✅ Acceptance Criteria

Scenario: Deploy MCP Elicitation server
  Given a new MCP Elicitation server is available
  When a client connects using the 2025-06-18 protocol
  Then the server supports all required elicitation endpoints and features

Scenario: Client initiates elicitation session
  Given the server is running
  When a client starts an elicitation session
  Then the server guides the client through the elicitation process as per the spec

---

🙋♂️ User Story 2

As a: Application developer
I want: to integrate my app with the MCP Elicitation server
So that: I can automate structured data collection and interactive workflows

✅ Acceptance Criteria

Scenario: App integrates with elicitation endpoints
  Given the app is configured with the MCP Elicitation server URL
  When the app sends elicitation requests
  Then the server responds according to the 2025-06-18 protocol

---

📐 Design Sketch (optional)

flowchart TD
    A[Client] -- Elicitation Request --> B(MCP Elicitation Server)
    B -- Elicitation Flow --> C[Workflow/Prompt Engine]
    C -- Response --> A

Loading

---

🔗 MCP Standards Check

• Change adheres to current MCP specifications
• No breaking changes to existing MCP-compliant integrations
• If deviations exist, please describe them below:

---

🔄 Alternatives Considered

• Continue using older MCP server versions (lacks new elicitation features)
• Custom, non-standard elicitation implementations (not interoperable)

---

📓 Additional Context

• See the MCP Elicitation v2025-06-18 specification
• Related issues: #elicitation, #mcp-server, #integration

[crivetimihai]

Thanks for providing a detailed set of requirements.

Duplicate of #234 - check out https://ibm.github.io/mcp-context-forge/architecture/roadmap/ - we'll track this requirement in #234.