# Connect from Claude, run long commands

URL: https://briq.cloud/blog/changelog-2026-10-17

> Week of 12 October: briq is in Claude's directory and the MCP Registry, commands can run for hours, and databases can be reached from outside.

By Sylvain Goumy, Founder of briq ([LinkedIn](https://www.linkedin.com/in/sylvain-goumy/), [X](https://x.com/goooums), [GitHub](https://github.com/goums)). Changelog, 17 October 2026.

Our first week in public. Here is what changed for you and your agents.

## Connect briq from Claude

briq is now in [Claude's connector directory](https://claude.ai/directory/briq). Open it, select
**Connect**, then sign in to briq and choose the team and the budget Claude gets. Nothing to paste.

It works in Claude on the web, on desktop and on mobile, and in Claude Code when it is signed in
with your Claude account. The connect steps on our site and in the dashboard now start with a
Claude tab. Other agents keep the install prompt.

## Listed in the MCP Registry

briq is in the official [MCP Registry](https://registry.modelcontextprotocol.io/v0/servers?search=cloud.briq)
as `cloud.briq/briq`, and on [Glama](https://glama.ai/mcp/connectors/cloud.briq/briq). A client
that reads the registry installs briq from there. It signs in through the browser: there is no
key to copy.

## Run commands that take minutes or hours

`briq_exec` waits for a command for up to a minute. A build, a test suite or a data load takes
longer. Now the agent starts it with `async: true` and checks on it until it ends.

```text
briq_exec({ briq: "bq_…", cmd: ["sh", "-c", "npm ci && npm test"], async: true })
→ ex_7kq2m9x1p4ab running since 10:02 UTC

briq_exec_result({ briq: "bq_…", exec: "ex_7kq2m9x1p4ab" })
→ ex_7kq2m9x1p4ab exited 0 after 3m
```

* **Up to 24 hours**: one hour by default, longer with `timeoutMs`.
* **Every line kept**: each check shows the end of the output, the whole of it stays in a file.
* **Stopped on request**: `briq_exec_stop` ends the command and every process it started.
* **No sleep in the middle**: a running command keeps its briq awake.

The guide: [Run a long command](https://briq.cloud/docs/guides/run-a-long-command).

## Long tool calls come back

Some MCP clients give a server 60 seconds to start answering. A `briq_run` waiting for a slow
service could pass that limit, and the client dropped the result. Our MCP server now streams its
answers, so a long call still returns.

## Reach a database from outside

Ask your agent for a connection string. It gives the database a TCP endpoint, over TLS:

```text
briq_expose({ briq: "bq_…", port: 5432, protocol: "postgres" })
→ postgres://postgres:…@db-k3m9x2p7qa.tcp.briq.run:5432/app?sslmode=require
```

* **Seven protocols**: Postgres, MySQL, Redis, MongoDB, RabbitMQ, Neo4j and gRPC.
* **Wakes on connect**: a sleeping database starts when a client connects.
* **On every plan**, with no limit on the number of endpoints.
* **In the dashboard**: the briq's **Endpoints** card, under **tcp**. The password stays hidden
  until you show it.

The guide: [Connect to a database from outside](https://briq.cloud/docs/guides/connect-to-a-database-from-outside).

## Agents see their screenshots

`briq_files_get` returns a PNG, JPEG, GIF or WebP file as an image. An agent that takes a
screenshot in a browser briq can now look at it. The new guide
[Drive a browser](https://briq.cloud/docs/guides/drive-a-browser) shows both ways to control one.

## Try it

**Claude**

1. Add briq to Claude:

[Connect in Claude](https://claude.ai/directory/briq)

2. Connect Claude to briq: sign in, or create your account and claim your €10 of free credits.

**Other agents**

1. Paste this prompt into your agent:

```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
```

2. Follow your agent's next steps: usually a restart, then a link to sign in.

**Try it**

- GitHub repo: "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."
- Reporting: "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." (Metabase is an open-source BI tool, like Tableau.)
- Postgres: "Start a Postgres for this project on briq (https://briq.cloud/cookbook/postgres.md) and connect the app to it."
- Web app: "Run this app on briq (https://briq.cloud/cookbook/node.md) and give me a preview link."
- Memory: "Start a SiYuan notebook on briq (https://briq.cloud/cookbook/siyuan.md), keep your notes on this project in it, and give me a link to browse them." (SiYuan is an open-source notes app, like Obsidian.)
- Planning: "Start a Plane board on briq (https://briq.cloud/cookbook/plane.md), turn our TODO list into issues, and give me a link to the board." (Plane is an open-source project board, like Linear.)

Tell us what to build next at [hello@briq.cloud](mailto:hello@briq.cloud), or ask your agent to
send it with `briq_feedback`.