How to Connect DBeaver to Claude Compliance via a JDBC Driver
The CData JDBC Driver for Claude Compliance implements JDBC standards that enable third-party tools to interoperate, from wizards in IDEs to business intelligence tools. This article shows how to connect to Claude Compliance data with wizards in DBeaver and browse data in the DBeaver GUI.
Create a JDBC Data Source for Claude Compliance Data
Follow the steps below to load the driver JAR in DBeaver.
- Open the DBeaver application and, in the "Database" menu, select the "Driver Manager" option. Click "New" to open the "Create new driver" form.
- In the Settings tab:
- Set Driver Name to a user-friendly name for the driver (e.g. CData JDBC Driver for Claude Compliance).
- Set Class Name to the class name for the JDBC driver: cdata.jdbc.claudecompliance.ClaudeComplianceDriver.
- Set URL Template to jdbc:claudecompliance:.
- In the Libraries tab, click "Add File," navigate to the "lib" folder in the installation directory (C:\Program Files\CData\CData JDBC Driver for Claude Compliance XXXX\) and select the JAR file (cdata.jdbc.ClaudeCompliance.jar).
Create a Connection to Claude Compliance Data
Follow the steps below to add credentials and other required connection properties.
- In the "Database" menu, click "New Database Connection."
- In the "Connect to a database" wizard that results, select the driver you just created (e.g. CData JDBC Driver for Claude Compliance) and click "Next >."
- On the Main tab of the configuration wizard, set the JDBC URL, using the required connection properties:
The driver connects to Claude Compliance using a Compliance Access Key, the only supported authentication method. Set the following connection property:
- APIKey: The Compliance Access Key you created.
Creating a Compliance Access Key
- Enable the Compliance API for your organization.
- Sign in to claude.ai as a primary owner or organization owner and open Organization settings > API > Keys.
- Select Create Key and assign only the scopes your integration needs:
- read:compliance_activities for Activities and the typed activity views.
- read:compliance_org_data for organizations, roles, groups, and settings.
- read:compliance_user_data for users, chats, files, projects, and downloads.
- delete:compliance_user_data for the explicit Delete stored procedures.
- Create the key and copy it when it appears. The key starts with sk-ant-api01- and is shown only once.
Optionally, set OrganizationUUID to limit organization-scoped views (such as OrganizationUsers and ComplianceRoles) to a single linked organization. If it is left empty, those views default to the first available organization and do not include data from all linked organizations.
Built-in Connection String Designer
For assistance in constructing the JDBC URL, use the connection string designer built into the Claude Compliance JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.
java -jar cdata.jdbc.claudecompliance.jarFill in the connection properties and copy the connection string to the clipboard.
Below is a typical connection string:
jdbc:claudecompliance:APIKey=your_compliance_access_key;
- Click "Test Connection ..." to ensure you have configured the connection properly.
- Click "Finish."
Query Claude Compliance Data
You can now query information from the tables exposed by the connection: Right-click a Table and then click View Table. The data is available on the Data tab.