# briq > briq gives coding agents real databases, browsers and whole apps in one MCP call: isolated, EU-hosted, billed by the second, with a capped budget. - MCP server (streamable HTTP): https://api.briq.cloud/mcp. Clients sign in through the browser (MCP OAuth), or send `Authorization: Bearer ` - REST API: https://api.briq.cloud/v1, OpenAPI document at https://api.briq.cloud/v1/openapi.json - Every page below is Markdown; the whole site in one file is https://briq.cloud/llms-full.txt ## Get started - [What is briq](https://briq.cloud/docs.md): The services your agent's work needs, through one MCP server your agent signs in to. - [Quickstart](https://briq.cloud/docs/getting-started.md): Connect your agent client to briq and run your first briq. - [Clients](https://briq.cloud/docs/setup/clients.md): Add briq to your MCP client and sign in. - [Frameworks](https://briq.cloud/docs/setup/frameworks.md): Connect an agent you build with an SDK to briq's MCP server, with an API key. - [For agents](https://briq.cloud/docs/setup/agents.md): For an AI agent setting briq up for its person. Add the server, get them signed in, check it works. ## Learn - [Briq](https://briq.cloud/docs/concepts/briq.md): One running OCI image on its own microVM. - [Stack](https://briq.cloud/docs/concepts/stack.md): A named group of briqs that can talk to each other. - [Recipes](https://briq.cloud/docs/concepts/recipes.md): Ready-made stacks that return connection strings, not Dockerfiles. - [Agents, keys and policy](https://briq.cloud/docs/concepts/keys-and-policy.md): What an agent can do, how it signs in, and who sets its policy. - [Lifecycle and sleep](https://briq.cloud/docs/concepts/lifecycle-and-sleep.md): States, moves, and the one setting that decides when a briq stops on its own. - [Forks](https://briq.cloud/docs/concepts/fork.md): Branch a briq, or a whole stack, before a change you might want to undo. - [Give Claude Code a database](https://briq.cloud/docs/guides/give-claude-code-a-database.md): Let the agent run migrations, seed data and test queries against a real Postgres. - [Run your own app](https://briq.cloud/docs/guides/run-your-own-app.md): Your code as a running service, with a URL, in one call and no image to build. - [Run a GitHub repo](https://briq.cloud/docs/guides/run-a-github-repo.md): An app from a repo, running with a URL. The briq downloads the code itself, and nothing is built on your side. - [Run tests against real services](https://briq.cloud/docs/guides/run-tests-against-real-services.md): Replace mocks with a real Postgres and Redis for the duration of a test run. - [Try a migration on a fork](https://briq.cloud/docs/guides/try-a-migration-on-a-fork.md): Let an agent run a risky change on a copy of the database, then keep it or throw it away. - [Expose a preview URL](https://briq.cloud/docs/guides/expose-a-preview-url.md): Give a running service an HTTPS URL, public or private. - [Connect to a database from outside](https://briq.cloud/docs/guides/connect-to-a-database-from-outside.md): A briq's database reachable from psql, a BI tool or an app elsewhere, over TLS, with a normal connection string. - [Report on a dataset](https://briq.cloud/docs/guides/report-on-a-dataset.md): Load a public dataset into Postgres, chart it in Metabase, and share a link to the dashboard. - [Budgets](https://briq.cloud/docs/guides/budgets.md): Hand an agent a budget instead of your account. ## Reference - [MCP tools](https://briq.cloud/docs/mcp/tools.md): Every tool the briq MCP server exposes, with input, output and an example call. - [REST API overview](https://briq.cloud/docs/api/overview.md): Base URL, authentication, errors and conventions. - [REST reference](https://briq.cloud/docs/api/reference.md): Every endpoint an agent uses under /v1. ## Operations - [Cost](https://briq.cloud/docs/cost.md): Per-second pricing, four sizes, one currency, and where the numbers show up. - [Security](https://briq.cloud/docs/security.md): Isolation model, what briq can see, abuse policy and responsible disclosure. - [Regions](https://briq.cloud/docs/regions.md): Where briqs run and how a team picks its region. ## Cookbook - [All recipes](https://briq.cloud/cookbook.md): the recipe index - [PostgreSQL](https://briq.cloud/cookbook/postgres.md): A PostgreSQL database with a persistent volume. Optional pgvector. - [MySQL](https://briq.cloud/cookbook/mysql.md): A MySQL database with a persistent volume. - [Redis](https://briq.cloud/cookbook/redis.md): A Redis server (Valkey-compatible) for caches and queues. - [MongoDB](https://briq.cloud/cookbook/mongo.md): A MongoDB server with authentication and a persistent volume. - [MinIO (S3)](https://briq.cloud/cookbook/minio.md): S3-compatible object storage with a web console. - [Mailpit](https://briq.cloud/cookbook/mailpit.md): Catches outgoing email for tests, with a web inbox and a JSON API. - [RabbitMQ](https://briq.cloud/cookbook/rabbitmq.md): AMQP message broker with the management UI enabled. - [Headless Chrome](https://briq.cloud/cookbook/chrome.md): A headless Chromium with a WebSocket endpoint for Playwright or Puppeteer. - [Redis + BullMQ dashboard](https://briq.cloud/cookbook/redis-bullmq.md): Redis for BullMQ queues, plus a Bull Board UI to inspect jobs. Point your workers at REDIS_URL; the dashboard discovers the queues itself. - [Neo4j](https://briq.cloud/cookbook/neo4j.md): A graph database with a persistent volume, for data an agent should query, not paraphrase. - [Pandoc](https://briq.cloud/cookbook/pandoc.md): A document converter with LaTeX, for a skill that has to produce a file, not just a plan for one. - [Plane](https://briq.cloud/cookbook/plane.md): A self-hosted Linear/Jira-like board the agent can update, with a link to share. - [Qdrant](https://briq.cloud/cookbook/qdrant.md): A vector database, for a knowledge file the agent can search by meaning, not grep. - [Wiki.js](https://briq.cloud/cookbook/wiki.md): A wiki the agent can write pages to and hand you a link into, instead of NOTES.md. - [Grafana](https://briq.cloud/cookbook/grafana.md): A dashboard the agent can point at its own data, instead of a STATUS.md it writes by hand. - [Metabase](https://briq.cloud/cookbook/metabase.md): Reports on a Postgres warehouse: load a dataset, build a dashboard, share a link to it. - [Memos](https://briq.cloud/cookbook/memos.md): A markdown note store with an API, for memory a human can read and the agent can append to. - [SiYuan](https://briq.cloud/cookbook/siyuan.md): A block-based knowledge workspace with a kernel API, for an agent vault a human can browse. - [Python app](https://briq.cloud/cookbook/python.md): Your Python code running as a service, from files or a GitHub repo: it installs requirements.txt and starts it. No image to build. - [Node.js app](https://briq.cloud/cookbook/node.md): Your Node.js code running as a service, from files or a GitHub repo: it installs package.json and starts it. No image to build. - [Bun app](https://briq.cloud/cookbook/bun.md): Your TypeScript or JavaScript running on Bun, from files or a GitHub repo: it installs package.json and starts it. No build step. - [Go app](https://briq.cloud/cookbook/go.md): Your Go code running as a service, from files or a GitHub repo: it builds the module and starts the binary. No image to build. - [Ruby app](https://briq.cloud/cookbook/ruby.md): Your Ruby code running as a service, from files or a GitHub repo: it bundles the Gemfile and starts it. No image to build. - [Rust app](https://briq.cloud/cookbook/rust.md): Your Rust crate running as a service, from files or a GitHub repo: it builds a release and runs it. No image to build. - [PHP app](https://briq.cloud/cookbook/php.md): Your PHP code served by PHP's built-in server, from files or a GitHub repo. No image to build. - [Static site](https://briq.cloud/cookbook/static.md): HTML, CSS, JavaScript and images served by nginx, from files or a folder of a GitHub repo. No build, no image. - [Nginx gateway](https://briq.cloud/cookbook/nginx.md): A gateway (reverse proxy): one URL for several briqs of a stack, routed by path (/api/ to the back end, / to the front end). One origin for the browser, nothing to change in the apps. ## Blog - [All posts](https://briq.cloud/blog.md): the blog index - [Introducing briq](https://briq.cloud/blog/introducing-briq.md): Why we are building a cloud for AI agents, and what comes next. ## Optional - [Cookies](https://briq.cloud/legal/cookies.md): What briq stores in your browser, and your choice about the analytics cookie. - [Data protection](https://briq.cloud/legal/data-protection.md): Where your data is processed, who can reach it, and which providers are involved. - [Data processing agreement](https://briq.cloud/legal/dpa.md): The Article 28 terms under which briq processes personal data on your behalf, including sub-processors and security measures. - [Legal notice](https://briq.cloud/legal/notice.md): Who publishes briq.cloud and who hosts it. - [Privacy notice](https://briq.cloud/legal/privacy.md): What personal data briq collects, why, for how long, and your rights over it. - [Terms of service](https://briq.cloud/legal/terms.md): The agreement between you and briq: what we provide, what you are responsible for, and what happens when something goes wrong.