zed -atexplore

This MCP server extension for Zed enables exploration of the AT Protocol ecosystem by connecting to the ATExplore MCP server. Once installed in Zed, the extension communicates with the ATExplore MCP server to surface MCP endpoints, capabilities, and related metadata within your Zed workspace, allowing you to navigate and interact with AT Protocol resources directly from your editor. Use the extension to browse available MCPs, inspect protocol details, and leverage ATExplore’s tooling to understand how MCPs expose commands, events, and schemas across the AT Protocol ecosystem.

To get started, install the ATExplore MCP extension for Zed from the Zed Extensions marketplace. After installation, configure the extension to point at the ATExplore MCP server (the default public endpoint is https://mcp.atexplore.social/mcp). Once configured, the extension will fetch the MCP context and present you with the server’s registered MCPs, their capabilities, and any associated documentation within Zed. You can then explore individual MCP endpoints, view sample requests, and trial interactions in your development environment.

Prerequisites:

• Node.js installed and available in your PATH
• Zed editor installed with Extensions marketplace access

Installation steps:

1. Open Zed and go to Extensions > Marketplace.
2. Search for the ATExplore MCP extension for Zed (the extension name includes ATExplore and Zed).
3. Click Install and wait for the extension to finish installing.
4. Open Zed settings for the extension and configure the MCP server URL if desired. Use the provided example configuration:

{ "context_servers": { "mcp-server-atexplore": { "settings": { "server_url": "https://mcp.atexplore.social/mcp" } } } }

5. Save the configuration and reload Zed if prompted. The extension will connect to the ATExplore MCP server and populate MCP data for exploration.

Tips and notes:

• The extension relies on the ATExplore MCP server. If you encounter connectivity issues, verify that the server_url is accessible and that there are no network restrictions blocking access.
• If you change the server_url later, reload the extension or Zed to refresh the MCP context.
• The extension may cache MCP metadata; cached data can be cleared by reloading the extension or clearing Zed's extension data.
• If you run into authentication or rate-limiting issues, consult ATExplore documentation for any required API keys or access controls and adjust the server_url or headers accordingly.