Brev MCP Server

The MCP server uses the Brev CLI's API access token and currently set org. The brev mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 2 defined tools rather than through you.

Its toolset

Everything the assistant can do here goes through one of these:

• Token — --token or UV_PUBLISH_TOKEN
• Debugging — Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the [MCP

Configuration

You will need one environment variable: UV_PUBLISH_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

The server ships on npm as @modelcontextprotocol/inspector, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Brev MCP's toolset — Token, Debugging — is a fair guide to whether it matches your workflow. It is maintained by brevdev; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Brev MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the brev mcp mcp server does with a few real requests.