Skip to content

Comments

Elicitation note okta-1117761#5988

Open
sophiajose-okta wants to merge 1 commit intomasterfrom
sj-okta-1117761
Open

Elicitation note okta-1117761#5988
sophiajose-okta wants to merge 1 commit intomasterfrom
sj-okta-1117761

Conversation

@sophiajose-okta
Copy link
Contributor

@sophiajose-okta sophiajose-okta commented Feb 24, 2026

Description:

  • **What's changed?**Added a note to support elicitation
  • Is this PR related to a Monolith release? 2026.03.0

Resolves:

Netlify Preview Link:

https://preview-5988--reverent-murdock-829d24.netlify.app/docs/guides/start-mcp-server/main/#example-commands

@okta-prod-github-app
Copy link

Acrolinx score

A minimum Acrolinx Score of 80 is required. The total score is an average of the subscores.
Select Total score to review the Acrolinx scorecard for your article. Try to increase your individual scores, for example: Correctness. Your content will be clearer and more consistent.

Article Total score
Required:80
Word and phrases
(Brand, terms)
Preferred: 80
Correctness
(Spelling, grammar)
Preferred: 80
Clarity
(Readability)
Preferred: 80
Inclusive language
(+ accesibility)
Preferred: 80
packages/@okta/vuepress-site/docs/guides/start-mcp-server/main/index.md 84 88 94 76

Successfully checked 1 of 1 documents.
See summary in Content Analysis Dashboard

Reopen the pull request or push new changes to check again.

Depending on the Acrolinx server configuration, the
links expire after some time and you must have a login for the
Acrolinx server to access them again.

@sophiajose-okta sophiajose-okta added the docs release Tagged to be released during scheduled docs release label Feb 24, 2026
>**Note:** All destructive actions such as deleting groups, apps, policies, policy rules, or deactivating and deleting users require explicit confirmation using the [MCP Elicitation API](https://modelcontextprotocol.io/specification/2025-06-18/client/elicitation). The confirmation experience depends on the client:
>
>* Clients that support elicitation: The user sees a native chat UI dialog to accept, decline, or cancel the request.
>* Clients that don’t yet support elicitation: The tool returns a JSON payload describing the pending action so the LLM can relay the confirmation request to the user.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
>* Clients that don’t yet support elicitation: The tool returns a JSON payload describing the pending action so the LLM can relay the confirmation request to the user.
>* Clients that don’t support elicitation: The tool returns a JSON payload describing the pending action so the LLM can relay the confirmation request to the user.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs release Tagged to be released during scheduled docs release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants