Brev MCP server
This is a MCP server implementation for Brev.
Configuration
The MCP server uses the Brev CLIβs API access token and currently set org.
Follow the Brev documentationβ to download the CLI and login if you havenβt already.
If you want to switch your Brev org, run brev set <org-name>
The CLI access token expires every hour. If you have any 403 errors, simply run brev ls
to refresh the access token.
Quickstart
Setup repository locally
git clone git@github.com:brevdev/brev-mcp.git
Install uv
Follow the uv installation guideβ
Claude Desktop
On MacOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json
On Windows: %APPDATA%/Claude/claude_desktop_config.json
Add the following to your claude_desktop_config.json
:
Development/Unpublished Servers Configuration
"mcpServers": {
"brev_mcp": {
"command": "uv",
"args": [
"--directory",
"<path-to-repo>",
"run",
"brev-mcp"
]
}
}
Development
Building and Publishing
To prepare the package for distribution:
- Sync dependencies and update lockfile:
uv sync
- Build package distributions:
uv build
This will create source and wheel distributions in the dist/
directory.
- Publish to PyPI:
uv publish
Note: Youβll need to set PyPI credentials via environment variables or command flags:
- Token:
--token
orUV_PUBLISH_TOKEN
- Or username/password:
--username
/UV_PUBLISH_USERNAME
and--password
/UV_PUBLISH_PASSWORD
Debugging
Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the MCP Inspectorβ.
You can launch the MCP Inspector via npm
with this command:
npx @modelcontextprotocol/inspector uv --directory /Users/tmontfort/Brev/repos/brev_mcp run brev-mcp
Upon launching, the Inspector will display a URL that you can access in your browser to begin debugging.