Skip to content

Commit 8a01cb3

Browse files
update
1 parent 3529e46 commit 8a01cb3

File tree

2 files changed

+23
-0
lines changed

2 files changed

+23
-0
lines changed
20.5 KB
Loading

docs/integrations/mcp.mdx

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -33,10 +33,33 @@ Add this JSON to your MCP client configuration file:
3333

3434
Alternatively, use the CLI command shown on the MCP integration page for your preferred tool (Claude Code, Codex, Copilot CLI, Gemini CLI, or VS Code).
3535

36+
## Authentication
37+
38+
To connect to Bytebase, you need to finish the authentication process via OAuth by logging into Bytebase and authorizing the AI to access your Bytebase account.
39+
40+
![mcp-auth](/content/docs/integrations/mcp/mcp-auth.webp)
41+
42+
Your tool will be connected to Bytebase once you click the Allow button.
43+
3644
## Usage
3745

3846
Once connected, try asking your AI assistant:
3947

4048
- "List all projects in my Bytebase instance"
4149
- "Show me the schema for database X"
4250
- "Generate a migration script to add a users table"
51+
52+
53+
## Important notes
54+
55+
<Warning>
56+
57+
Caution: Once connected, your AI assistant will inherit all your permissions in Bytebase, including making changes to database or updating settings (in the case of an admin). So be cautious when instructing AI assistant to apply any change via Bytebase.
58+
</Warning>
59+
60+
<Warning>
61+
62+
Audit logging: any action taken by the AI assistant via MCP will be audit-logged in Bytebase under your account.
63+
64+
</Warning>
65+

0 commit comments

Comments
 (0)