FinalStandards Track
| Field | Value |
|---|---|
| SEP | 973 |
| Title | Expose additional metadata for Implementations, Resources, Tools and Prompts |
| Status | Final |
| Type | Standards Track |
| Created | 2025-07-15 |
| Author(s) | @jesselumarie |
| Sponsor | None |
| PR | #973 |
Abstract
This SEP proposes adding two optional fields—icons and websiteUrl. The icons and websiteUrl would be added to the Implementation schema so that clients can visually identify third-party implementations and link directly to their documentation. The icons parameter will also be added to the Tool, Resource and Prompt schemas. While this can be used by both servers and clients for all implementations, we expect it to be used initially for server-provided implementations.
Motivation
Current State
Current implementations only expose namespaced metadata, forcing clients to display generic labels with no visual cues.Proposed State
The proposed implementation would allow us to add visual affordances and links to documentation, making it easier to visually identify which servers/clients are providing an implementation e.g. a tool in a slash command interface:- Visual Affordance: Icons make it immediately clear to users which tool or resource source is in use.
- Discoverability: A link to documentation (
websiteUrl) allows clients to direct users to more information with a single click.
Rationale
This design builds on prior work in web manifests (MDN) and consolidates community feedback:- Consolidation of PRs: Merges the changes from PR #417 and PR #862 into a single, cohesive enhancement.
- Flexible Icon Sizes: Supports multiple icon sizes (e.g.,
48x48,96x96, oranyfor vector formats) to accommodate different client UI needs. - Optional Fields: By making both fields optional, existing implementations remain fully compatible.
Specification
Extend theImplementation object as follows:
Tool, Resource and Prompt interfaces with the following type: