LoginSign Up
← Back to all sparks
B

Bytebase

INFRA · APIS
Velocity6.3

Database CI/CD and schema change management platform

www.bytebase.com ↗

Bytebase lets MCP agents request and approve database access, with the user confirming.

database governancemcpai agentsaccess controlapprovals
◆Current state
Bytebase is a database change and access governance platform whose recent releases center on approval flows and its MCP server. 3.23 added a workspace MCP policy (Disabled, Read-only, Read-write), 3.23.1 made direct DDL/DML in SQL Editor an explicit opt-in, and 3.24 lets agents in Read-write mode run access requests end to end. 3.24 also makes TLS settings for SQL Server and Oracle actually apply.
◆Where it's heading
Bytebase is turning its governance controls into something agents can operate, while keeping the user's own permissions and project approval rules as the limit. Each step so far has paired more agent capability with a matching off switch or confirmation step.
◆Prediction
Expect more of the change workflow, such as creating and deploying plans, to become available to MCP agents under the same confirm-in-client rule.

◆Recent moves

  1. 6d ago

    Bytebase 3.24: MCP agents can request and approve access

    ⚡ SPARK

    3.24 builds on the 3.23 MCP access policy: in Read-write mode an agent can request just-in-time access, approve or reject issues, and manage masking exemptions, with the user confirming in their MCP client. It moves Bytebase's agent support from reading data to operating the approval workflow itself.

    View source ↗
  2. 21d ago

    SQL Editor direct DDL/DML execution becomes an explicit opt-in

    3.23.1 turns the ambiguous Environments field on DDL/DML roles into an explicit Direct DDL/DML execution switch, off by default, after owners routinely granted approval-free execution everywhere by accident. It applies the safe-default logic of the MCP policy to human roles, alongside clearer task run logs and plan review comments.

    View source ↗
  3. 1mo ago

    MCP access policy: disable, read-only or read-write per workspace

    Adds a workspace-level MCP access policy (Disabled, Read-only, Read-write), with new workspaces defaulting to Read-only. It extends the governance arc from human approvals to AI-client sessions.

    View source ↗
  4. 1mo ago

    GPT-5 support and searchable service accounts in grant picker

    GPT-5 support for AI features and searchable service accounts in the grant picker. Maintenance-grade, but it keeps the AI assistant current while the access-grant flow gets smoother.

    View source ↗
  5. 2mo ago

    Worksheets become Saved Queries with per-object sharing

    Worksheets become Saved Queries with per-user and per-group Viewer/Editor sharing, folders and favorites. The SQL Editor gains the same object-level permission model the rest of the product is moving toward.

    View source ↗
  6. 2mo ago

    DynamoDB gets per-instance AWS credentials and role ARNs

    DynamoDB connections gain per-instance AWS credentials and cross-account role ARNs, plus a batch of fixes. Broadens multi-account coverage for a non-SQL engine.

    View source ↗