aedibase-mcp
v0.1.0
Published
MCP server for aedibase — expose your scale-to-zero, Supabase-compatible backend to AI coding agents (Claude Code, Cursor, …). Create apps, run SQL, manage storage/functions/migrations. Zero-install via npx.
Maintainers
Readme
aedibase-mcp
MCP server for aedibase — gives an AI coding agent (Claude Code, Cursor, Windsurf, …) direct tools to run your scale-to-zero, Supabase-compatible backend: create apps, run SQL, inspect schema, manage storage / edge functions / migrations / backups.
You normally don't run this directly — install it into your agent with one command:
npx aedibase-install --client claude-code --env AEDIBASE_TOKEN=aedu_...That registers npx -y aedibase-mcp in your client's MCP config.
Config
The server reads (in order: CLI flag → env → ~/.aedibase/credentials.json):
| | |
|---|---|
| AEDIBASE_TOKEN / --token | your API token (aedu_…), minted in the console or via npx aedibase-cli login |
| AEDIBASE_URL / --url | control plane, default https://app.aedify.ai |
The token is user-scoped: an agent can only ever touch your own apps. There is no platform-admin path.
Tools (30)
create_app · list_apps · get_app · execute_sql · describe_app ·
wake_app · sleep_app · reactivate_app · delete_app · get_status ·
generate_types · get_logs · storage_upload/list/url/delete ·
create_bucket · list_buckets · set_bucket_policy · delete_bucket ·
migration_new/list/apply · function_deploy/list/delete ·
backup_now/list · restore_backup · get_instructions.
Tell your agent to call get_instructions first — it returns the aedibase
usage guide (REST/auth grammar, RLS one-liner, storage, workflow).
Apps nap to 0 RAM when idle and wake on the next call (~1-3s cold) — the tools handle this transparently. Zero dependencies; Node ≥ 18.
