db

A command for setting up or querying a Lovable project's cloud database, which is a hosted Postgres database.

In plain words
What is it for?
Use it to check database status, enable a database, run supplied SQL, or retrieve connection details.
Why use it?
It makes database work explicit and requires confirmation before SQL that changes data or the database structure is run.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/lovablelabs/mcp/db
Clone the repo
git clone --depth 1 https://github.com/lovablelabs/mcp
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 179 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00013 $0.00179
Opus 5 $0.00006 $0.00089
Sonnet 5 $0.00003 $0.00036
Haiku 4.5 $0.00001 $0.00018

Measured yesterday against content hash 5be8a27f8d14, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

db scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/db.md · 13 lines

What it actually says

Work with a Lovable project's database. Input: $ARGUMENTS

  1. Resolve the project_id (use list_projects if the user gave a name).
  2. Call get_database_status. If no database exists and the user wants one, confirm and call enable_database (takes 30–60s; one-time per project).
  3. If the user supplied SQL, run it with query_database.
    • ⚠️ query_database has full read / write / schema permissions. Show the user the exact SQL and get explicit confirmation before running anything that writes data or alters schema.
  4. For connection details (connection string, API URL), call get_database_connection_info.
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 13 lines · 13 tokens per session scan A 5be8a27f8d14

Subscribe to this mod's changes

db is a command published in the GitHub repository lovablelabs/mcp (3 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 179 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.