Grok Lantern Works GPU Prices: daily GPU rental price comparison optimize_stack
How to: Grok Lantern Works GPU Prices: daily GPU rental price comparison optimize_stack
Add Lantern Works GPU Prices: daily GPU rental price comparison to Grok
-
01
Open .mcp.json (in your project root) and merge this in. Keep any servers already there.
{
"mcpServers": {
"lantern-works-deals": {
"type": "http",
"url": "https://lantern-works-mcp.lantern-works.workers.dev/mcp?ref=mcp-registry"
}
}
}-
02
Save the file and restart Grok.
-
03
Ask for something optimize_stack does. Grok lists the server's tools on connect and calls optimize_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.
Grok Build reads Claude Code's .mcp.json and Claude Desktop's config unchanged, so a server you have already set up there needs nothing new. The Grok web app and X integration do not take custom servers. Grok docs
Set these first
Lantern Works GPU Prices: daily GPU rental price comparison will not start until these are set, so optimize_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 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.