VS Code Lantern Works GPU Prices: daily GPU rental price comparison optimize_agent_stack
How to: VS Code Lantern Works GPU Prices: daily GPU rental price comparison optimize_agent_stack
Add Lantern Works GPU Prices: daily GPU rental price comparison to VS Code
-
01
Open .vscode/mcp.json and merge this in. Keep any servers already there.
{
"servers": {
"lantern-works-deals": {
"type": "http",
"url": "https://lantern-works-mcp.lantern-works.workers.dev/mcp?ref=mcp-registry"
}
}
}-
02
Save the file and restart VS Code.
-
03
Ask for something optimize_agent_stack does. VS Code lists the server's tools on connect and calls optimize_agent_stack itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that Lantern Works GPU Prices: daily GPU rental price comparison's identifier in your config matches the one above exactly.
Requires agent mode. MCP: Open User Configuration puts the same block in every workspace. VS Code docs
Set these first
Lantern Works GPU Prices: daily GPU rental price comparison will not start until these are set, so optimize_agent_stack never becomes available.
-
LANTERN_DEALS_FILE -
LANTERN_GPU_PRICES_FILE
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 5 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.