Everything hellodb can do, callable.
Every operation the canvas performs is an entry on a typed API, and the same entries are published as MCP tools. An agent can create a schema, add models and relations, read the canvas back and cut a version without touching the interface.
MCP server
Streamable HTTP. Point any MCP client at the endpoint below — no wrapper, no shim.
https://api.hellodb.io/bridge/mcp
REST
Every operation is a POST that takes and returns JSON. Failures return a structured error with a stable code, whatever the status.
# No authentication required
curl -s -X POST https://api.hellodb.io/bridge/health.check
{ "ok": true, "database": "connected" }
# Authenticated calls carry the session cookie from Google sign-in
curl -s -X POST https://api.hellodb.io/bridge/schema.list \
-H 'content-type: application/json' \
-b 'token=<session>' \
-d '{"filter":"mine","query":"shop","limit":12}'
{ "rows": [ ... ], "total": 3, "hasMore": false }Machine-readable files
32 operations, each with a unique operationId, typed arguments and a typed response schema. Generated from the server’s own definitions, so it cannot drift.
Server descriptor: transport, endpoint, authentication and the full tool list.
What hellodb is for, when an agent should reach for it, and — as importantly — when it should not.
Every public page, including all 24 playground schemas.
Authentication
A session cookie, issued by Google sign-in at /sign-in. health.check and public.get need none. API keys for headless agents are not issued yet.
Try it without an account
The playground opens 16 real product schemas on a fully editable canvas, with no sign-up. Each is a JSON document in the same shape the API returns.