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:
Add an MCP prompt picker in the composer or integrations menu.
Load prompts from the selected MCP server with prompts/list.
If a prompt requires arguments, collect them before the message is sent.
On send, resolve the selected prompt with prompts/get.
Inject the returned prompt messages into the current turn only.
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.
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
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @ultramancode on GitHub (Apr 22, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/23984
Check Existing Issues
Verify Feature Scope
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:
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:
prompts/list.prompts/get.Alternatives Considered
None
Additional Context
@ultramancode commented on GitHub (Apr 22, 2026):
I opened a follow-up PR for this issue: #23985