Repository navigation
Icon support in web client #784
Description
Is your feature request related to a problem? Please describe.
Currently, MCP servers can define icons in their server.json configuration file (as per the MCP server schema), but these icons are not displayed in the new official UI client. This creates a less visually appealing and less intuitive experience when browsing or selecting MCP servers in the registry or connector list. Users cannot easily identify servers by their visual branding, making it harder to distinguish between different MCP servers at a glance.
Describe the solution you'd like
I would like the MCP registry UI clients to support displaying icons defined in the server.json configuration file. Specifically:
-
Icon Display in Connector Lists: When users browse available MCP servers in the connector/registry interface, each server should display its configured icon (if available) next to the server name and description.
-
Icon Support for Multiple Formats: Support for the icon configuration format as defined in the MCP server schema, including:
- Multiple icon sizes (e.g.,
sizes: ["45x44"]) - Different MIME types (e.g.,
image/png,image/svg+xml) - Theme-specific icons (e.g.,
theme: "light"ortheme: "dark")
- Multiple icon sizes (e.g.,
-
Fallback Behavior: If an icon is not available or fails to load, the UI should gracefully fall back to a default icon or placeholder.
-
Icon Caching: Icons should be cached appropriately to improve performance and reduce load times.
Describe alternatives you've considered
- No Icons: Continue without icon support. This maintains the status quo but misses an opportunity to improve user experience and visual branding.
Additional context
- The MCP server schema already supports icon definitions in
server.json(as seen in the MCP server schema documentation) - Many MCP servers (including JustCall MCP Server) already have icons configured in their
server.jsonfiles - Icon support would improve:
- User Experience: Easier visual identification of servers
- Brand Recognition: Better branding opportunities for MCP server providers
- Professional Appearance: More polished and modern UI
- Accessibility: Visual cues can help users with different learning styles
Related Files:
- MCP Server Schema:
https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json - Example server.json with icons: See
server.jsonin this repository
Activity
feat(web): display package icons in server list
feat(ui): display server icons in the registry web client
tounsils commentedon Aug 27, 2026
Happy to take this one if nobody is on it.
The schema has supported
iconsfor a while and the web client just never rendered them, so the change is confined toui_index.html. Approach I went with:validateIconalready rejects other schemes at publish, but this UI can be pointed at a staging, local or custom API base URL from its own settings, so the scheme is re-checked rather than trusted.sizes: ["any"]is preferred, otherwise the smallest icon at least as wide as the rendered size, so it stays crisp without pulling a needlessly large file.theme: "dark"used only as a fallback, since this UI has a light background.srcthrough the existingescapeAttr, emptyalt(the icon sits beside the server name, so repeating it is noise for screen readers),loading="lazy",referrerpolicy="no-referrer", and a broken image removes itself rather than leaving a placeholder.Tested the selection against the first 100 servers in the production registry, which happens to cover every shape published today: no
sizesfield, a single512x512,["any"], and a256/512pair. Also checked thathttp,javascript:,data:and null sources render nothing.PR incoming. Happy to change the approach if you had something different in mind.
feat(ui): display server icons in the registry web client (modelconte…
fix(ui): prefer human-readable server title in registry cards (#1573)