l4 mcp

l4 mcp wires a coding agent to your cloud spend so you can ask it questions in the editor you already use. It writes the client configuration for you rather than leaving you to hand-edit JSON.

l4 mcp install     # add the server to the agent clients on this machine
l4 mcp status      # show what is wired up, and what is not
l4 mcp uninstall   # take it back out
l4 mcp serve       # run the server locally over stdio

Which command you want

l4 mcp install is the one to reach for when you want a key installed across every client on the machine in a single step. Run it once, restart your client, and ask it what you are spending this month.

l4 mcp status is the first thing to run when an agent reports no LevelFour tools. It reports, per client, whether it is installed and whether it carries a LevelFour entry.

l4 mcp uninstall removes the entry again, and can delete the dated backups that still hold a previous key.

l4 mcp serve runs the server on your own machine. install points Claude Desktop at it automatically, because that client starts stdio servers and cannot send an Authorization header to a remote one. You rarely run it by hand.

Supported clients

Claude Code, Claude Desktop, Cursor, VS Code and Windsurf. Any other client that speaks MCP over streamable HTTP connects the same way, by hand. See Connecting a client for the configuration each one expects.

Related

• MCP server - the hosted surface, its tools and its prompts
• Connecting a client - signing in, keys, and per-client configuration
• Approving a connection - what the browser asks when you sign in
• Tools - every tool the server registers