Provides a Brev-based MCP server that authenticates via Brev CLI and exposes an MCP-compliant endpoint for local development.
Configuration
View docs{
"mcpServers": {
"brev_mcp": {
"command": "uv",
"args": [
"--directory",
"<path-to-repo>",
"run",
"brev-mcp"
]
}
}
}This Brev MCP Server lets you run a local MCP server that integrates with Brev’s API-backed environment. It uses the Brev CLI for authentication and a standard MCP runtime to expose your server to MCP clients. It’s designed to be run locally and debugged with tooling that supports MCP protocols, while keeping token lifecycle simple through the Brev CLI.
You can connect an MCP client to your Brev MCP Server by running the local server through your MCP toolchain. Start by ensuring you are authenticated with Brev and that your access token is refreshed regularly. If you encounter a 403 error, refresh your token by listing your orgs with the Brev CLI.
To run the Brev MCP Server locally, you can configure a local MCP runtime to execute the server process using the following setup. This example shows how to point a development MCP runtime to your local repository and start the server. You can adapt this to your environment or IDE that supports MCP configurations.
{
"mcpServers": {
"brev_mcp": {
"command": "uv",
"args": [
"--directory",
"<path-to-repo>",
"run",
"brev-mcp"
]
}
}
}A debugging tool that connects to the running MCP server and provides a browser-based interface to inspect requests, responses, and flow while debugging MCP interactions.