briq

cloud.briq由 briq.cloud 发布官方发布者v1.0.2更新于 Oct 24, 2026

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

已验证Streamable HTTP可网页运行数据库云端与基础设施开发者工具

概览

AI 生成的概览

托管型 MCP 服务器，让助手一次调用就能拥有自己的云资源：Postgres、Redis、沙箱、Docker 镜像或 GitHub 应用。

可以做什么
  • 创建与管理 briq：运行配方或任意 OCI 镜像并返回连接串，启动、停止、复制、销毁及设置休眠时间
  • 在 briq 内执行命令、读取日志、写入或读取文件
  • 将 briq 发布为 HTTPS 网址、带令牌的网址或 TCP 端点
  • 查看正在运行的内容、状态与已产生费用，以及额度、限制和助手预算
  • 浏览配方目录、阅读 briq 文档，并按名称引用团队密钥而不暴露其值
适用场景
适合助手需要独立临时基础设施的场景：为项目启动数据库、在沙箱中运行测试和构建而不占用本机，或快速部署仓库或 Docker 镜像并给出可分享的链接。
运行要求
远程 Streamable HTTP 端点 api.briq.cloud/mcp，无需本地安装包。首次使用需通过浏览器 MCP OAuth 登录，并选择团队与助手预算。在无浏览器或 CI 环境中，需在 Authorization 头中携带来自 Agents 页面的 API 密钥。需要带额度的 briq 账户。
安装前请注意
按秒计费并受每个助手的预算限制，从少量赠送额度开始，费用会持续累积。助手可创建、公开暴露、复制和销毁基础设施，并执行任意命令与镜像，均属写入操作。密钥通过凭据网关按名称引用，服务器称不会返回值。数据与工作负载运行在第三方欧盟托管服务上。

安装

在 SourceWeft 中

  1. 打开 控制台中的 briq，将其添加到工作区。
  2. 连接 所需的 凭据。它们会被私密存储，绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/cloud.briq%2Fbriq/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。

{
  "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.

来源：README.md，提交 51f2b9e

工具

0
该服务器需要登录，因此 SourceWeft 无法在没有账号的情况下读取其工具，也未收录。已连接账号所能看到的内容可能因账号及其权限而异。

版本历史

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

评分

已满足适用检查项的 85%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分