# l4 mcp

> Wire the agent clients on this machine to the LevelFour MCP server: install it, check it, remove it, or serve it locally.

Source: https://docs.levelfour.ai/cli/commands/mcp


`l4 mcp` wires the agent clients on this machine to your cloud spend, so you can ask about it in the client you already use. It writes the client configuration for you rather than leaving you to hand-edit JSON.

> **Note**
>
> [`l4 mcp install`](/cli/commands/mcp/install) connects clients with a LevelFour API key. Signing in through the browser is the other credential, and it writes nothing to disk. [Connecting a client](/mcp/authentication) compares them.

## Subcommands

| Command                                           | What it does                                                                          | Reach for it when                                               |
| ------------------------------------------------- | ------------------------------------------------------------------------------------- | --------------------------------------------------------------- |
| [`l4 mcp install`](/cli/commands/mcp/install)     | Writes the server into every client it can confirm on this machine                    | You want every client wired in one step                         |
| [`l4 mcp status`](/cli/commands/mcp/status)       | Reports, per client, whether it is installed and whether it carries a LevelFour entry | You have just installed, or an agent reports no LevelFour tools |
| [`l4 mcp uninstall`](/cli/commands/mcp/uninstall) | Removes the entry, and can delete the dated backups that still hold a previous key    | You are taking it back out, or a backup still holds an old key  |
| [`l4 mcp serve`](/cli/commands/mcp/serve)         | Relays the hosted server over stdio on your own machine                               | Rarely by hand. `install` points Claude Desktop at it           |

## Clients it configures

`install`, `status` and `uninstall` know Claude Code, Claude Desktop, Cursor, VS Code and Windsurf. Any other client that speaks MCP over streamable HTTP reaches the same server, [configured by hand](/mcp/authentication).

## Related

* [MCP server](/mcp): the hosted surface, its tools and its prompts
* [Connecting a client](/mcp/authentication): signing in, keys, and per-client configuration
* [Approving a connection](/mcp/approving-a-connection): what the browser asks when you sign in
* [Tools](/mcp/tools): every tool the server registers
* [CLI overview](/cli): installing `l4`, the global flags, and the exit codes