briq

briq

Give your agent its own cloud.
Postgres, Redis, a sandbox to run code in, an app from a GitHub repo, or any Docker image, each on its own microVM, in one MCP call.

Docs · Cookbook · MCP tools · Dashboard

https://api.briq.cloud/mcp

A 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.md

Or install it as a plugin:

Client	Install
Claude Code	/plugin marketplace add briq-cloud/briq-mcp, then /plugin install briq@briq
Claude (web, desktop, mobile)	Connect from Claude's connector directory
VS Code (GitHub Copilot)	briq in GitHub's MCP Registry, also in VS Code's MCP gallery
Gemini CLI	gemini extensions install https://github.com/briq-cloud/briq-mcp
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.

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 sandbox on briq (https://briq.cloud/cookbook/sandbox.md), clone this project into it, run the test suite there instead of on my machine, and tell me what fails.

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
briq_run	Run a recipe or any OCI image; returns connection strings
briq_exec	Run a command inside a briq
briq_logs	Read a briq's logs
briq_files_put / briq_files_get	Write or read a file in a briq
briq_expose	Publish a briq: an HTTPS URL, public or behind a token, or a TCP endpoint for Postgres
briq_fork	Copy a briq or a whole stack, its disk included, before a risky change
briq_set_sleep	Set when a briq sleeps (30m, 7d, or never)
briq_stop / briq_start / briq_destroy	Lifecycle
briq_list / briq_status	What runs, its state, its cost so far
briq_catalog	The recipe cookbook
briq_quota	Credits, limits and the agent's budget
briq_secrets	The team's secrets by name and allowed hosts, never a value: a briq names one and the credential gateway puts the value in on the way out
briq_docs	Read briq's docs
briq_feedback	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. Or a sandbox: a microVM with Python, Node, git and a shell, where the agent runs scripts, tests and builds instead of on your machine (guide).

• 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: [email protected] · Security reports: [email protected]

The files in this repository are MIT licensed. The briq service is operated by Uplab SAS under its terms.