Zed norway location transport mcp resolve_stop_place
How to: Zed norway location transport mcp resolve_stop_place
Add norway location transport mcp to Zed
-
01
Open ~/.config/zed/settings.json and merge this in. Keep any servers already there.
{
"context_servers": {
"norway-location-transport-mcp": {
"url": "https://norway-location-transport-mcp.met-mcp-worker.workers.dev/mcp"
}
}
}-
02
Save the file and restart Zed.
-
03
Ask for something resolve_stop_place does. Zed lists the server's tools on connect and calls resolve_stop_place itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that norway location transport mcp'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
norway location transport mcp will not start until these are set, so resolve_stop_place never becomes available.
-
ET_CLIENT_NAME
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.