Four ways to use Bytebase: Console, API, MCP, Terraform (2/7)

BytebaseOct 23, 2026

Get Started

Four ways to use Bytebase (2/7)

Bytebase is one control plane between your users and your databases. However you connect, the same permissions, masking, and audit trail apply.

Bytebase sits between its consumers — human, AI agent, and application — and databases like PostgreSQL, MySQL, and Oracle, reached through one control plane via GUI, MCP server, or API.

Console

The web UI for everyday work — propose and approve changes, run queries, and manage projects and access.

API

A REST API over the same operations for scripts and CI; machines authenticate with a service account key or short-lived workload-identity tokens — no stored secret.

MCP server

Built in at /mcp. Point Claude Code, Cursor, or any MCP client at it — it authorizes through Bytebase, so reads stay masked and every action is audited.

Terraform provider

Codifies the control plane — projects, users, IAM, masking, approval and SQL review rules — so governance config lives in version control.

Explore the Docs

Bytebase — the standard for database governance.