Zed Communicate Developer Docs communicate_get_openapi_summary
How to: Zed Communicate Developer Docs communicate_get_openapi_summary
Add Communicate Developer Docs to Zed
-
01
Open ~/.config/zed/settings.json and merge this in. Keep any servers already there.
{
"context_servers": {
"communicate-docs": {
"url": "https://communicate.so/mcp"
}
}
}-
02
Save the file and restart Zed.
-
03
Ask for something communicate_get_openapi_summary does. Zed lists the server's tools on connect and calls communicate_get_openapi_summary itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that Communicate Developer Docs's identifier in your config matches the one above exactly.
Merge this into your existing settings object — do not replace the file. Zed docs
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 8 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.