Zed McpStamp Leave Tracker leave_request
How to: Zed McpStamp Leave Tracker leave_request
Add McpStamp Leave Tracker to Zed
-
01
Open ~/.config/zed/settings.json and merge this in. Keep any servers already there.
{
"context_servers": {
"leave": {
"url": "https://mcp.zovo.one/mcp/leave"
}
}
}-
02
Save the file and restart Zed.
-
03
Ask for something leave_request does. Zed lists the server's tools on connect and calls leave_request itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that McpStamp Leave Tracker's identifier in your config matches the one above exactly.
Merge this into your existing settings object — do not replace the file. Zed docs
Set these first
McpStamp Leave Tracker will not start until these are set, so leave_request never becomes available.
-
MCP_LICENSE_KEY
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.