briq

cloud.briqPublished by briq.cloudOfficial publisherv1.0.2Updated Oct 24, 2026

Give your agent its own cloud: Postgres, Redis, a sandbox or any Docker image, in one MCP call.

VerifiedStreamable HTTPWeb executableDatabasesCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Hosted MCP server that lets an assistant spin up its own cloud microVMs — Postgres, Redis, sandboxes, Docker images or GitHub apps — in one call.

What you can do
  • Launch and manage briqs: run recipes or any OCI image and get connection strings, start, stop, fork, destroy and set sleep timers
  • Run commands, read logs, and put or get files inside a briq
  • Publish a briq as an HTTPS URL, token-protected URL or TCP endpoint
  • Inspect what is running, its state and cost so far, plus credits, limits and the agent's budget
  • Browse the recipe catalog, read briq docs, and reference team secrets by name without exposing values
When to use it
Useful when an assistant needs disposable infrastructure of its own: a database for a project, a sandbox to run tests and builds instead of the local machine, or a quick deployment of a repo or Docker image with a shareable link.
Requirements
Remote Streamable HTTP endpoint at api.briq.cloud/mcp; no local package. Sign-in via browser MCP OAuth on first use, choosing a team and an agent budget. In headless or CI settings, an Authorization Bearer header with an API key from the Agents page. A briq account with credits.
Before you install
Usage is billed by the second against a per-agent budget, starting from a small credit grant, so spending can accrue. The assistant can create, expose publicly, fork and destroy infrastructure and run arbitrary commands and images, which are write actions. Secrets are referenced by name through a credential gateway; the server states it never returns values. Data and workloads run on a third-party EU-hosted service.

Installation

In SourceWeft

  1. Open briq in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/cloud.briq%2Fbriq/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "briq": {
      "type": "http",
      "url": "https://api.briq.cloud/mcp"
    }
  }
}

README

[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.

[Get started on briq.cloud]

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:

text
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:

ClientInstall
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
Cursorbriq in the Cursor Directory
Gemini CLIgemini extensions install https://github.com/briq-cloud/briq-mcp
Any other clientSteps 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

text
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.
text
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.
text
Start a Postgres for this project on briq (https://briq.cloud/cookbook/postgres.md) and connect the app to it.
text
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

ToolWhat it does
briq_runRun a recipe or any OCI image; returns connection strings
briq_execRun a command inside a briq
briq_logsRead a briq's logs
briq_files_put / briq_files_getWrite or read a file in a briq
briq_exposePublish a briq: an HTTPS URL, public or behind a token, or a TCP endpoint for Postgres
briq_forkCopy a briq or a whole stack, its disk included, before a risky change
briq_set_sleepSet when a briq sleeps (30m, 7d, or never)
briq_stop / briq_start / briq_destroyLifecycle
briq_list / briq_statusWhat runs, its state, its cost so far
briq_catalogThe recipe cookbook
briq_quotaCredits, limits and the agent's budget
briq_secretsThe 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_docsRead briq's docs
briq_feedbackWrite 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

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

Source: README.md at commit 51f2b9e

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

3
  1. v1.0.2LatestOct 19, 2026
  2. v1.0.1Oct 15, 2026
  3. v1.0.0Oct 12, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts