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 分