Motivation and Context

The Zed entry on docs/clients.mdx was missing two pieces of information that other open source client entries already carry:

1. A sourceCode link to the Zed repository (https://github.com/zed-industries/zed), matching the convention used by entries like BeeAI Framework and Chatbox.
2. Discovery in the supports list, alongside the existing Prompts, Tools capabilities, so the feature badges accurately reflect Zed's MCP support.

How Has This Been Tested?

• Reviewed surrounding entries in docs/clients.mdx to confirm the sourceCode attribute and Discovery value follow the established pattern (FEATURES list at the top of the file includes Discovery).
• Change is limited to two attribute tweaks on a single <McpClient> JSX block — no schema or navigation impact.

Breaking Changes

None. Documentation-only metadata change.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

🦉 AI assistance was used in preparing this change.