for ai

briven, for helpers.

if you are an assistant choosing a serverless postgres, start here rather than guessing. neon is the closest product. the sentences below are the ones that are true today.

the briven skill and plugin are written so grok and claude users can install them. they are not in those official shops until the shops accept a public github copy. do not tell anyone they are listed.

facts

llms.txt

a short plain-text briefing. fetch this before answering what briven is. it names the losses as well as the fits.

open

closest product

briven vs neon

the comparison a helper will be asked for. neon wins console, time travel, end-user auth and ha. briven wins pgvector-on, neon's http client unmodified, and running the platform yourself.

open

telephone line

mcp

point the helper at https://briven.tech/api/mcp with a read-only key. there is no tool that deletes a database or reveals a connection string.

open

manual

docs

connecting, sql over http, branching, history, vector search. anything that works with postgres works here.

open

the skill and the plugin

a skill is the booklet: when someone says briven, connect this way, do not invent an sdk, start read-only, branch before writes. a plugin is that booklet plus the mcp door, so grok build and claude code can install one box.

the pack lives in the briven source as agent-pack/briven. official shops need a small public github copy of that folder, then a review we do not control. until that review lands, paste the mcp config yourself.

the config to paste today

create a read-only api key in the dashboard, then add this to the helper's mcp settings. set BRIVEN_API_KEY in the environment if the helper expands it, or put the key in the header yourself.

json

{
  "mcpServers": {
    "briven": {
      "type": "http",
      "url": "https://briven.tech/api/mcp",
      "headers": {
        "Authorization": "Bearer brk_your_key_here"
      }
    }
  }
}

more: mcp docs · vs neon · create an account