github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-07-16 14:39:31 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #23984] feat: Add MCP prompt support in chats #123450

New Issue
Closed
opened 2026-05-21 02:44:23 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-05-21 02:44:23 -05:00
Owner
Copy Link

Originally created by @ultramancode on GitHub (Apr 22, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/23984

Check Existing Issues

  • I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.

Verify Feature Scope

  • I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.

Problem Description

Open WebUI already supports MCP servers for tools and related capabilities, but there is still no direct chat UX for MCP prompts.

If an MCP server exposes prompts, users currently cannot:

  • browse available prompts from chat
  • fill in prompt arguments before sending
  • apply a selected prompt only to the current turn
  • tell which MCP prompt was used from the composer or message history

This leaves an important MCP capability underexposed in the main chat workflow.

This is especially noticeable when building or testing MCP server integrations, where server-defined prompts are often part of the workflow but cannot currently be invoked directly from chat.

Desired Solution you'd like

Add a dedicated MCP prompt flow in chat:

  1. Add an MCP prompt picker in the composer or integrations menu.
  2. Load prompts from the selected MCP server with prompts/list.
  3. If a prompt requires arguments, collect them before the message is sent.
  4. On send, resolve the selected prompt with prompts/get.
  5. Inject the returned prompt messages into the current turn only.
  6. Preserve the selected prompt in message metadata and show a visible MCP prompt indicator in the composer and sent message history.

Alternatives Considered

None

Additional Context

Originally created by @ultramancode on GitHub (Apr 22, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/23984 ### Check Existing Issues - [x] I have searched for all existing **open AND closed** issues and discussions for similar requests. I have found none that is comparable to my request. ### Verify Feature Scope - [x] I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions. ### Problem Description Open WebUI already supports MCP servers for tools and related capabilities, but there is still no direct chat UX for MCP prompts. If an MCP server exposes prompts, users currently cannot: - browse available prompts from chat - fill in prompt arguments before sending - apply a selected prompt only to the current turn - tell which MCP prompt was used from the composer or message history This leaves an important MCP capability underexposed in the main chat workflow. This is especially noticeable when building or testing MCP server integrations, where server-defined prompts are often part of the workflow but cannot currently be invoked directly from chat. ### Desired Solution you'd like Add a dedicated MCP prompt flow in chat: 1. Add an MCP prompt picker in the composer or integrations menu. 2. Load prompts from the selected MCP server with `prompts/list`. 3. If a prompt requires arguments, collect them before the message is sent. 4. On send, resolve the selected prompt with `prompts/get`. 5. Inject the returned prompt messages into the current turn only. 6. Preserve the selected prompt in message metadata and show a visible MCP prompt indicator in the composer and sent message history. ### Alternatives Considered None ### Additional Context - MCP prompts are part of the official MCP server capability model. - Related references: - MCP prompts specification: https://modelcontextprotocol.io/specification/2025-06-18/server/prompts - Claude Desktop / MCP documentation: https://support.claude.com/en/articles/11175166-get-started-with-custom-integrations-using-remote-mcp
GiteaMirror commented 2026-05-21 02:44:24 -05:00
Author
Owner
Copy Link

@ultramancode commented on GitHub (Apr 22, 2026):

I opened a follow-up PR for this issue: #23985

<!-- gh-comment-id:4294500466 --> @ultramancode commented on GitHub (Apr 22, 2026): I opened a follow-up PR for this issue: #23985
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#123450
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?