briq
OfficialAllows running Bun applications on a briq microVM.
Allows running any public OCI or Docker image as a briq microVM.
Allows deploying an application from a GitHub repository onto a briq microVM.
Provides a ready-made recipe to start Grafana for dashboards and monitoring.
Provides a ready-made recipe to start Metabase for analytics and reporting.
Provides a ready-made recipe to start MinIO for S3-compatible object storage.
Provides a ready-made recipe to start MongoDB as a document database.
Provides a ready-made recipe to start MySQL as a relational database.
Provides a ready-made recipe to start Neo4j as a graph database.
Allows running PHP applications on a briq microVM.
Allows running Python applications on a briq microVM.
Provides a ready-made recipe to start RabbitMQ as a message broker.
Provides a ready-made recipe to start Redis as an in-memory data store or cache.
Allows running Ruby applications on a briq microVM.
Allows running Rust applications on a briq microVM.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@briqStart a Postgres for this project and give me the connection string."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
https://api.briq.cloud/mcpA hosted, remote MCP server (Streamable HTTP). Your client signs in through the browser with MCP OAuth; no key to copy. This repository holds the connection config for MCP registries and plugin stores. The server itself runs at the URL above.
Connect
Paste this into your agent. It edits its own MCP config, then tells you what is left:
Add the briq MCP server to your config:
- name: "briq"
- url: https://api.briq.cloud/mcp (Streamable HTTP, OAuth)
- for all my projects
Then tell me what to do next to connect and activate it. If needed, read the setup instructions for agents: https://briq.cloud/docs/setup/agents.mdOr install it as a plugin:
Client | Install |
Claude Code |
|
Claude (web, desktop, mobile) | |
Gemini CLI |
|
Any other client | Steps per client: briq.cloud/docs/setup/clients |
On first use, your browser opens: sign in or sign up, then pick the team and the budget the agent gets.
On a server or in CI, where no browser can open, send Authorization: Bearer <BRIQ_API_KEY> with a key
from the Agents page.
Related MCP server: Cloud Harness MCP
Try
Deploy briq-cloud/wall github repo on briq (https://briq.cloud/docs/guides/run-a-github-repo.md) and give me a link to it.Start a Postgres for this project on briq (https://briq.cloud/cookbook/postgres.md) and connect the app to it.Start Metabase on briq (https://briq.cloud/cookbook/metabase.md), load 'Our World in Data' energy dataset into it, generate a report on world energy generation, and share it with me.Tools
Tool | What it does |
| Run a recipe or any OCI image; returns connection strings |
| Run a command inside a briq |
| Read a briq's logs |
| Write or read a file in a briq |
| Publish a briq: an HTTPS URL, public or behind a token, or a TCP endpoint for Postgres |
| Copy a briq or a whole stack, its disk included, before a risky change |
| Set when a briq sleeps ( |
| Lifecycle |
| What runs, its state, its cost so far |
| The recipe cookbook |
| Credits, limits and the agent's budget |
| Read briq's docs |
| Write to the briq team |
Full reference with inputs and outputs: briq.cloud/docs/mcp/tools.
What runs
Any public OCI image, plus ready-made recipes that return connection strings, not Dockerfiles: Postgres, MySQL, Redis, MongoDB, MinIO, Qdrant, Neo4j, RabbitMQ, a headless Chrome, Mailpit, Metabase, Grafana and more, and your own code in Node, Bun, Python, Go, Ruby, Rust, PHP or a static site, from files or from a GitHub repo.
Isolated: each briq is its own microVM; each team has its own private network.
Sleeps when idle: a briq stops when nobody uses it and wakes on the next call or request.
Budgets: billed by the second, against a budget you set per agent.
EU-hosted by default, with other regions available.
Start with €10 of credits. Pricing: briq.cloud/docs/cost.
Links
REST API:
https://api.briq.cloud/v1(OpenAPI)Docs for agents: briq.cloud/llms.txt
Security: briq.cloud/docs/security · Privacy: briq.cloud/legal/privacy
Contact: hello@briq.cloud · Security reports: security@briq.cloud
The files in this repository are MIT licensed. The briq service is operated by Uplab SAS under its terms.
This server cannot be deployed
Maintenance
Related MCP Connectors
Hosted MCP runtime where your agent publishes its own tools by tool call and keeps working.
Hosted MCP catalog with 30 tenant-isolated browser, RAG, AI, mail and media tools.
Create, deploy, and operate MCP servers directly from your GitHub repositories.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Related MCP Servers
AlicenseAqualityCmaintenanceProvides MCP tools to create, run commands in, checkpoint, and delete durable cloud environments, giving coding agents persistent state between calls.751 npm3MIT- AlicenseNot gradedqualityAmaintenanceEnables AI clients to securely operate isolated coding workspaces with file, command, Git, and deployment tools via authenticated remote MCP.72MIT
- AlicenseAqualityBmaintenanceEnables AI agents to perform software engineering tasks inside an isolated, deterministic sandbox—exploring repositories, reproducing failures, applying patches, running tests, and verifying solutions against hidden suites through MCP tools.8MIT
- AlicenseNot gradedqualityAmaintenanceEnables agents to create, inspect, and stop local multi-service preview environments with stable URLs via MCP tools.225 npmMIT