MySQL DB Browser

MySQL DB Browser lets admins register external MySQL connections, inspect schemas, browse table contents, and run controlled queries from the Syrus admin UI. Credentials are stored encrypted and connections are explicit per database target.

This plugin is separate from Admin MySQL: Admin MySQL inspects Syrus' own runtime database, while MySQL DB Browser is for operator-managed external databases that Syrus may need to inspect.

Agentic DB Browser tools include mysql_db_browser_list_connections, which returns safe metadata only for agentic-enabled connections in the caller's credential scope (id, label, default_database, agentic_access_enabled, allow_writes, and timestamps). Agents should call it before schema browsing or query execution so they do not have to guess a mysql_connection_id. Query execution remains read-only by default, but safe diagnostic statements such as SHOW, DESCRIBE, and EXPLAIN SELECT ... are accepted without enabling writes.

What It Adds

• Admin UI and API endpoints for MySQL connection management.
• Connection URL paste support for mysql:// and mysql2:// URLs.
• Schema browsing for databases, tables, and columns.
• Controlled query execution against configured external connections.

When To Enable

Enable this plugin when Syrus operators need a lightweight database browser for external MySQL systems. Keep it disabled when all database access should remain outside Syrus.

Operational Notes

Treat configured credentials as sensitive production access. New and rotated secrets are stored through the Credential Store plugin and default to the creator's user scope. Admins can select repository, team, or instance scope. Existing credential-backed connections retain instance scope until narrowed; legacy encrypted connection payloads are admin-only until an admin re-enters the password in Edit to migrate and scope them. Use narrowly scoped MySQL users for each connection whenever possible.