MCP Icon

MCP Icons are part of the metadata that a server provides to a client during the handshake. They allow AI applications to provide a better user experience by visually distinguishing between different data sources.

Representation

In the initialize response, a server includes its info:

{
  "name": "GitHub Explorer",
  "version": "1.0.0",
  "capabilities": {...}
}

While the core protocol focus is on capabilities, many hosts (like HasMCP or Claude Desktop) expect servers to provide icon URLs or base64 encoded images to enhance the integration dashboard.

Best Practices

• Format: SVG is preferred for scalability and themes.
• Visibility: Icons should be legible in both light and dark mode contexts common in AI IDEs.
• Branding: Unique icons help users quickly identify which server is being called during tool execution.

Questions & Answers

Why do MCP servers provide icon metadata to clients?

Icons allow AI applications to provide a significantly better user experience by visually distinguishing between different data sources and tools in their integration dashboards or chat interfaces.

When is icon information shared between the server and the host?

Icon and branding information is typically shared during the initial connection handshake, often within the server info block of the initialize response.

What are the best practices for preparing an MCP icon?

SVG is the preferred format for scalability across different themes. Icons should be designed for high legibility in both light and dark modes, and they should be unique enough to aid in quick brand identification.