Zed wsdot mcp server wsdot_get_border_waits
How to: Zed wsdot mcp server wsdot_get_border_waits
Add wsdot mcp server to Zed
-
01
Open ~/.config/zed/settings.json and merge this in. Keep any servers already there.
{
"context_servers": {
"wsdot-mcp-server": {
"url": "https://wsdot.caseyjhand.com/mcp"
}
}
}-
02
Save the file and restart Zed.
-
03
Ask for something wsdot_get_border_waits does. Zed lists the server's tools on connect and calls wsdot_get_border_waits itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that wsdot mcp server'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
wsdot mcp server will not start until these are set, so wsdot_get_border_waits never becomes available.
-
WSDOT_ACCESS_CODE -
MCP_LOG_LEVEL
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.