GitHub Repo
Open WebUI Community Proposes MCP Citation Field Mapping to Reduce Retrieval Services’ Dependence on the Events API
On October 8, the Open WebUI community proposed an administrator-configured MCP citation mapping that would generate source markers directly from existing retrieval results. The project’s response noted that the Events API already supports citations; the new approach remains a partial prototype and is not yet an official feature.
A new discussion about Open WebUI shifts the focus of MCP knowledge base integration to how sources are displayed. On October 8, a community member proposed administrator-configured citation field mapping. The following day, Classic298 replied that external MCP tools can already send sources through the Events API. The proposal’s practical value, then, is reducing integration coupling; it should not be interpreted as meaning the platform does not support MCP citations at all. Community discussion
The official documentation explains that external OpenAPI and MCP tools can send source events to the event endpoint for a specified chat message. Once ENABLE_FORWARD_USER_INFO_HEADERS is enabled, tool requests include chat and message identifiers. Source data uses two corresponding arrays, document and metadata, to represent passages and links. This path supports the native tool-calling mode, but the service must understand Open WebUI’s event interface. Events documentation
The new proposal instead lets the connection settings specify the field names for the results list, title, body, URL, and document identifier. The host first parses the JSON inside the MCP text content, then uses the mapping to create source events and group them by document. For retrieval services with an established response format, or those operating through an MCP gateway, this could reduce the work required to modify a server for a single chat interface. Limiting the mapping to a specified connection and tool also avoids applying citation parsing based solely on a tool’s name. Proposal and prototype
Deployments must also distinguish between “tool return content” and “tool-sent citation events.” The official development documentation says that, in native mode, only fixed built-in tools automatically generate sources from results; Python tools can still send citations explicitly. The self.citation flag mentioned in older tutorials no longer has any effect. When investigating missing citations, engineers should first confirm which data path is in use. Tool development documentation
The mapping approach is currently only a partial test by its author on v0.11.4, not a PR. Follow-up questions include whether upstream will adopt it, whether the settings can be retained in the admin interface, and how well it works with large result sets and third-party MCP services. For enterprise RAG teams, the factors worth evaluating are citation traceability and the cost of service coupling. For now, the official Events API remains the verifiable basis for integration. Testing limitations