Nubase CLI
A CLI connects Claude Code and Codex to Nubase, installing skills and MCP tools for databases, functions and app deployment.
- 620 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- The agent gains actions over SQL, users, storage, functions and public application files.
Install
- Works in
Manual install
npx -y nubase_cli@latest install-skillsInstalls skills and MCP configuration, then opens browser sign-in. Check which project you authorize.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The agent gains actions over SQL, users, storage, functions and public application files.
This is third-party code. Review the repository files before installing.
What it does
Nubase CLI installs skills and an MCP connection for a selected Nubase project. After authorization, an agent can inspect schemas, run SQL, manage access and storage, deploy functions and publish static application files. Nubase itself provides a backend with PostgreSQL, authentication, storage and other modules. The CLI connects that service to a coding agent. Users can choose a hosted instance or supply their own Studio and API endpoints during setup.
Who it is for. For developers managing a Nubase project through an AI agent with explicitly granted permissions.
Good fit when
- Create tables for a test application.
- Let an agent inspect a Nubase schema.
- Deploy a function in a selected project.
- Publish a prepared frontend through Assets.
Not a fit when
- You cannot authorize database, user or function changes.
- You only need a local file generator without a backend.
- The selected project’s data cannot be exposed to an agent.
Example request
Connect a test Nubase project and show its schema without writes, deployment or user changes.Limitations
A reachable Nubase instance and authorized project are required; CLI installation does not automatically provision all server infrastructure. MCP exposes broad database, account and deployment actions, so start with a separate test project. The chosen server handles data and credentials and needs appropriate permissions before connection. Assets publishing makes files public; inspect the build and remove private configuration before authorizing an upload.
How to disable. Remove the nubase connection and installed skills, then revoke project authorization. Deployed functions and files require separate server removal.
FAQ
What does setup install?
Claude Code and Codex skills plus MCP configuration, then opens authorization.
How do I check Claude Code?
After restarting, run `/mcp` and locate nubase.
Where is Codex configured?
In `~/.codex/config.toml`.
Can I use my own server?
Yes. Supply `--studio-url` and `--nubase-url`.
Are scheduled jobs supported?
The backend supports cron jobs invoking an edge or database function.
Discussion
No questions or reviews yet.
Related
CLI toolsZCF
ZCF - Zero-Config Code Flow
A CLI that sets up Claude Code and Codex in one run: workflows, agents, skills, MCP and a provider choice
Indexes a codebase into a knowledge graph and gives the agent call chains, change blast radius and code search over MCP
A Codex and Claude Code plugin for 1C development: skills and an MCP server for metadata, forms, roles, DCS, data processors and running 1C
CodeNib indexes a repository and gives Claude Code and Codex ranked context with files and lines plus a graph of call chains
An HTTP gateway for Claude Code and Codex switches API endpoints on failure and converts requests between model formats
A kit for porting a Claude Code workflow to OpenAI Codex CLI for multi-tenant PHP/Bitrix24-Marketplace projects
README in short
The CLI bridges to Nubase. The server and its modules are deployed and updated separately from the AI-client connection.