zed -atproto-docs

This MCP server extension for Zed acts as a bridge to the ATproto Docs MCP server, enabling Zed users to search and query AT Protocol documentation through the MCP framework. The extension routes requests to the remote ATproto Docs MCP server and surfaces documentation results inside Zed, facilitating rapid lookup of AT Protocol concepts, endpoints, and usage notes. Use the provided tools to perform keyword searches, fetch protocol spec snippets, and retrieve example queries or usage patterns documented by the AT Protocol community.

To use it, ensure the MCP server is running and that Zed is configured to connect to this MCP server. Interact with Zed’s MCP tools or UI to issue search terms (e.g., “query, endpoints, or docs”) and view structured results returned from the remote ATproto Docs MCP server. The integration is designed to be lightweight and focuses on delivering documentation snippets, definitions, and references directly within your Zed environment.

Prerequisites:

• Node.js installed on your system (recommended LTS).
• Access to the repository hosting this MCP server extension and any required dependencies.
• Zed editor installed if you plan to use this extension within Zed.

Installation steps:

1. Clone or download this MCP server extension:

git clone https://github.com/your-org/zed-atproto-docs-mcp-server.git
cd zed-atproto-docs-mcp-server

2. Install dependencies (if any):

npm install

3. Run the MCP server extension (adjust command/path as needed):

node path/to/server.js

4. Verify the MCP server is reachable from your MCP client configuration and that it can connect to the remote ATproto Docs MCP server.

If you plan to containerize this extension, you can create a Dockerfile and build an image, then run it with a suitable port mapping and environment variables as required by your environment.

Tips and considerations:

• Ensure network access from the MCP server to the remote ATproto Docs MCP server is allowed (firewall, VPN, etc.).
• If the remote server requires authentication, configure the appropriate environment variables or config files as needed by the server implementation.
• Monitor logs for any connectivity or protocol errors between the local MCP server extension and the remote ATproto Docs MCP server.
• If you customize environment variables, document them in the mcp_config under env with clear descriptions, e.g., API keys or timeouts.
• Keep the MCP server updated to stay compatible with changes in the ATproto Docs MCP server API.