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
Thanks for the feedback. We've had a bit of trouble with ProGuard. 1.0.1 is already submitted to Store and waiting approval. Thanks for your patience! :)
Personally, I never had a problem with setting up the company, but I know many who did. Unfortunately, it is after the fact that the troubles start with various conflicting things and bureaucracy. Not panicking tho, every problem is here to be solved :)
Thanks for the feedback and good wishes. I agree that "generic reading" isn't the usual use case for this particular app. However we've found that a lot of people actually do want a mobile docs browser after their (great) experience with Dash on Mac.
The problem is that the new API doesn't seem to allow access to the console - if you point me up to the relevant docs, we'll definitely get it in for the next release! I am not really up for using an older version of API as it might (or might not) be deprecated soon :)
Can you please show me what do you mean by "the hamburger menu"? We have tried to stay away from complex gestures as we don't have an intro "tutorial", but we'll definitely listen to your suggestions.
Thanks for the compliments and comments btw, you guys are amazing!