Danilo Leal
6c6bc030c0
While creating a new MCP extension this weekend, I visited these pages and it felt like they could be improved a little bit. I'm renaming the MCP-related page under the /extension directory to use the "MCP" acronym, instead of "context servers". Release Notes: - N/A
1.5 KiB
MCP Server Extensions
Model Context Protocol servers can be exposed as extensions for use in the Agent Panel.
Defining MCP Extensions
A given extension may provide one or more MCP servers.
Each MCP server must be registered in the extension.toml:
[context_servers.my-context-server]
Then, in the Rust code for your extension, implement the context_server_command method on your extension:
impl zed::Extension for MyExtension {
fn context_server_command(
&mut self,
context_server_id: &ContextServerId,
project: &zed::Project,
) -> Result<zed::Command> {
Ok(zed::Command {
command: get_path_to_context_server_executable()?,
args: get_args_for_context_server()?,
env: get_env_for_context_server()?,
})
}
}
This method should return the command to start up an MCP server, along with any arguments or environment variables necessary for it to function.
If you need to download the MCP server from an external source—like GitHub Releases or npm—you can also do that in this function.
Available Extensions
Check out all the MCP servers that have already been exposed as Zed extensions on Zed's site.
We recommend taking a look at their repositories as a way to understand how they are generally created and structured.
Testing
To test your new MCP server extension, you can install it as a dev extension.