Set up a Claude Developer Platform connector

C1 provides identity governance and just-in-time provisioning for Claude Developer Platform. Integrate your Claude Developer Platform instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access.

This connector is in beta. This means it’s undergoing ongoing testing and development while we gather feedback, validate functionality, and improve stability. Beta connectors are generally stable, but they may have limited feature support, incomplete error handling, or occasional issues.

We recommend closely monitoring workflows that use this connector and contacting our Support team with any issues or feedback.

Capabilities

The Claude Developer Platform connector syncs the following resources:

Resource	Sync	Provision
API Keys
Organization Roles
Users
Workspaces

Gather Claude Developer Platform credentials

To configure the Claude Developer Platform connector, you need administrator permissions in Claude Developer Platform.

1. Log in to the Claude Platform Console with an account that has administrator permissions.

2. Under the Manage heading, navigate to API Keys > Admin keys and click Create Admin Key.

3. Enter any name for the key (for example, C1) and click Add.

   You must create an Admin key, not a regular API key. Admin keys have full access to the Admin API and do not have configurable scopes or permissions.

4. Copy the key and save it securely. You will not be able to view it again.

Configure the Claude Developer Platform connector

Cloud-hosted

Follow these instructions to use a built-in, no-code connector hosted by C1.

1. In C1, navigate to Integrations > Connectors and click Add connector.

2. Search for Claude Developer Platform and click Add.

3. Choose how to set up the new Claude Developer Platform connector:

   • Add the connector to a currently unmanaged app
   • Add the connector to a managed app
   • Create a new managed app
4. Set the owner for this connector.

5. Click Next.

6. Find the Settings area of the page and click Edit.

7. Enter the required configuration:

   • API Key: Your Claude Developer Platform API key
8. Click Save.

9. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

Done. Your Claude Developer Platform connector is now pulling access data into C1.

Self-hosted

Follow these instructions to use the Claude Developer Platform connector, hosted and run in your own environment.

When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals.

Step 1: Set up a new Claude Developer Platform connector

1. In C1, navigate to Integrations > Connectors > Add connector.

2. Search for Baton and click Add.

3. Choose how to set up the new Claude Developer Platform connector:

   • Add the connector to a currently unmanaged app
   • Add the connector to a managed app
   • Create a new managed app
4. Set the owner for this connector.

5. Click Next.

6. In the Settings area of the page, click Edit.

7. Click Rotate to generate a new Client ID and Secret.

   Carefully copy and save these credentials.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your Claude Developer Platform connector deployment:

Secrets configuration

# baton-claude-developer-platform-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-claude-developer-platform-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>

  # Claude Developer Platform credentials
  # Add connector-specific credentials here

  # Optional: include if you want C1 to provision access using this connector
  BATON_PROVISIONING: true

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-claude-developer-platform.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-claude-developer-platform
  labels:
    app: baton-claude-developer-platform
spec:
  selector:
    matchLabels:
      app: baton-claude-developer-platform
  template:
    metadata:
      labels:
        app: baton-claude-developer-platform
        baton: "true"
        baton-app: claude-developer-platform
    spec:
      containers:
      - name: baton-claude-developer-platform
        image: public.ecr.aws/conductorone/baton-claude-developer-platform:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-claude-developer-platform
        envFrom:
        - secretRef:
            name: baton-claude-developer-platform-secrets

Step 3: Deploy the connector

1. Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.

2. Check that the connector data uploaded correctly. In C1, click Applications. On the Managed apps tab, locate and click the name of the application you added the Claude Developer Platform connector to. Claude Developer Platform data should be found on the Entitlements and Accounts tabs.

Done. Your Claude Developer Platform connector is now pulling access data into C1.

---

All versions of this connector are available at dist.conductorone.com.