Hey Vedran. You connect to the database the same way you always did - when the agent spins up, you get a port, and you just point your MCP servers at it.
DATABASE_URL="postgres://localhost:15432/mydb"
That's it. The MCP server doesn't know or care about rmBug.
The one extra thing: by setting RMBUG_API_KEY in your environment, AI agents like Claude Code can spin up the rmBug agent themselves - no manual rmbug connect needed. The agent handles auth and port allocation autonomously, then your MCP tools connect through it as normal.
RMBUG_API_KEY="rmb_agent_..." # lets Claude Code spin up the agent
DATABASE_URL="postgres://localhost:15432/mydb" # MCP servers connect here