Skip to content
VelerionVelerion Docs

Browse & Install Servers

Search the catalog

Section titled “Search the catalog”
Terminal window
velerion mcp search postgres
ID                     VERSION  TRANSPORT        REVIEW      TOOLS
velerion/postgres      2.4.1    streamable-http  verified    6
community/pg-analytics 0.9.0    stdio            unreviewed  11

Add --reviewed-only to hide entries that have not passed a Velerion security review, and --workspace to restrict the search to servers your organisation has published privately.

Inspect before installing

Section titled “Inspect before installing”
Terminal window
velerion mcp show velerion/postgres@2.4.1 --tools

Read the side-effect column carefully. query is read-only; execute can write. Attaching a server does not by itself grant an agent the mutating half of its surface.

Install into an environment

Section titled “Install into an environment”

Installation binds the server to a connection, which is where the credential lives. The server never sees the raw secret — it receives a short-lived scoped token.

Terminal window
# 1. Create the connection that holds the credential.
velerion connection create warehouse-ro \
  --type postgres \
  --env staging \
  --secret DATABASE_URL


# 2. Install the pinned server version against it.
velerion mcp install velerion/postgres@2.4.1 \
  --env staging \
  --connection warehouse-ro

Attach it to an agent

Section titled “Attach it to an agent”
velerion.config.ts
import { defineAgent, mcp } from '@velerion/sdk';


export default defineAgent({
  name: 'support-triage',
  model: 'claude-opus-5',
  tools: [
    mcp('velerion/postgres', {
      connection: 'warehouse-ro',
      // Allow-list is explicit: anything not named here is not exposed.
      tools: ['query', 'describe_table'],
    }),
  ],
});

Upgrading a pinned version

Section titled “Upgrading a pinned version”
Terminal window
velerion mcp upgrade velerion/postgres --env staging --to 2.5.0
velerion mcp diff velerion/postgres 2.4.1 2.5.0

mcp diff reports added, removed and schema-changed tools. A removed tool that your agent allow-lists is a breaking change: the deployment is rejected rather than silently degraded.