MCP Metadata

MCP Metadata refers to the non-functional properties associated with protocol entities. This data helps host applications (clients) optimize how they present and manage servers.

Common Metadata Examples

• Logo/Icon: A URL or base64 icon for UI display.
• Tags: Categories like "database", "social", or "utilities".
• Documentation: Links to the server's README or setup guide.
• Supported Models: Hints on which LLMs work best with the server's tools.

Extensibility

While the core MCP spec defines specific metadata (like name and version), the protocol is designed to be extensible, allowing platforms like HasMCP to add proprietary metadata for advanced tracking and billing.

Questions & Answers

What is "MCP Metadata," and how does it differ from functional protocol data?

Metadata refers to non-functional properties associated with resources, tools, or prompts. Unlike functional data (like tool arguments), metadata is used by host applications to optimize UI presentation, categorizing tools, and providing context.

What are some common examples of metadata in an MCP server?

Common examples include logos or icons for visual display, tags for categorization (e.g., "social", "database"), links to external documentation, and hints about which LLM models work best with specific tools.

Is the MCP metadata schema extensible for third-party platforms?

Yes, the protocol is designed for extensibility. Platforms like HasMCP can add custom metadata fields to support advanced features like billing, enterprise-level tracking, or specialized governance policies.