Skip to main content

Introduction

With the Labellerr MCP Connector, you can import data directly from your Amazon S3 buckets, Google Cloud Storage buckets, or shared Google Drive links using natural language:
Example Prompt
Claude orchestrates the entire flow: it guides you to Labellerr’s secure credential interface, identifies the saved connection, creates the dataset, and tracks the import until the data is ready for annotation.
Zero-Credential Chat Security: Your cloud credentials never pass through Claude or the chat window. AWS access keys and GCS service-account keys are entered solely within Labellerr’s encrypted web interface. Claude is explicitly instructed to refuse credentials pasted into chat, and the MCP connector exposes no tools that accept secret keys.

How It Works

Connection Flow
1

Ask Claude to connect storage

Claude calls connect_cloud_source and returns a direct link to the Create Dataset screen of the Labellerr web console, along with step-by-step instructions.
2

Save connection in Labellerr

In the Labellerr web app, you paste your credentials, click Test Connection, and save the connection. Labellerr validates your credentials before saving.
3

Claude identifies the connection

Once you notify Claude that the connection is saved, Claude invokes list_connections. The newest connection appears at the top; Claude sees only its ID and human-friendly name.
4

Claude triggers the import

You specify the target folder within the bucket (e.g. retail/shelves/), and Claude invokes dataset_create. Labellerr launches an asynchronous import job and returns a job_id.
5

Claude notifies you upon completion

Claude periodically checks get_job_status (or dataset_get) until the dataset enters ready status. You can immediately launch an annotation project on the new dataset.
Already have saved connections? You can skip setup entirely. Just ask: “Which S3 connections do I have?” and tell Claude to import from an existing connection.

Before You Start: Cloud Permissions

Ensure your bucket credentials provide the necessary read permissions for Labellerr.

Amazon S3

Create an IAM User or IAM Role with the following permissions on your target bucket: For detailed AWS IAM setup instructions, refer to our AWS S3 Connection Guide.

Google Cloud Storage (GCS)

Generate a Service Account JSON key file with the following IAM roles or permissions: For detailed Google Cloud IAM setup, refer to our GCS Connection Guide.

Step 1: Save a Connection in Labellerr

Ask Claude:
or
Claude calls connect_cloud_source and provides a direct URL and guided steps:
  1. Open the link provided by Claude and sign in to Labellerr if requested.
  2. Enter any placeholder dataset name, choose your data type (e.g., Image), and click Next.
  3. Select Amazon S3, then click Create new connection.
  4. Enter your Access Key ID, Secret Access Key, and the S3 path (s3://your-bucket-name/path/to/data/). Click Test Connection.
  5. When the test succeeds, enter a memorable connection name (e.g. retail-prod-s3) and click Save.
  6. Click Cancel to exit the Create Dataset wizard (the connection remains securely saved in your workspace).
  7. Return to Claude and say: “Done, the connection is saved.”
Use descriptive names for connections (such as retail-shelves-s3 or autonomous-vehicles-gcs). Claude will display these names when listing available storage.

Step 2: Import a Dataset

Claude calls list_connections, retrieves the newly saved connection, and prompts for the subfolder to import:
Example Prompt
Claude invokes dataset_create with: The dataset is initialized in processing status. Labellerr scans the target path and imports all files matching the specified data type (for images: .jpg, .jpeg, .png, .tiff).

Step 3: Monitor Import Status

Imports run on Labellerr cloud servers, so they proceed even if you close Claude or shut down your computer. You can check progress at any time:
Prompt
Claude queries get_job_status (or dataset_get):

Google Drive Import

You can import datasets directly from Google Drive without setting up IAM policies or cloud access keys:
Available: Google Drive links can be imported directly through Claude!

How to Use Google Drive Import

  1. In Google Drive, right-click the folder or file you wish to import.
  2. Select Share → Share, and set General Access to “Anyone with the link” (Viewer permission).
  3. Copy the link and share it directly with Claude:
Example Prompt

Specifications and Limits

  • Maximum Files: Up to 2,500 images per import.
  • Maximum Size: Up to 2.5 GB total dataset size.
  • Supported Formats: JPG, JPEG, PNG, TIFF.
  • Error Handling: Links not set to “Anyone with the link” fail immediately with an explicit permission error. Claude reports any skipped or unreadable files alongside the reason.

Security Architecture

Credentials never touch Claude, the conversational prompt, or the MCP connector layer. Access keys and service accounts are transmitted over HTTPS directly to Labellerr’s backend and stored encrypted in accordance with SOC 2 compliance standards.
Claude can only see metadata returned by list_connections: connection ID, connection label/name, provider (s3 or gcs), connection type, and creation date. Folder paths passed in chat are visible to Claude, so avoid using proprietary identifiers in bucket path strings if needed.
Claude inherits your authenticated Labellerr workspace identity. It cannot access connections belonging to other workspaces or projects where you lack permissions.
The MCP connector intentionally does not expose deletion tools to prevent accidental loss. To delete a connection, remove it via the Labellerr web console under Settings → Data Connections or use the Labellerr Python SDK.

Troubleshooting

  • Ensure you saved the connection under the exact same workspace you selected when signing in to Claude.
  • Ask Claude: “List my S3 connections” or “List my GCS connections” to see all registered connections.
  • AWS S3: Verify that the Access Key and Secret Key are active and possess s3:GetObject and s3:ListBucket permissions. Ensure the bucket path uses s3://bucket-name/folder/ format with a trailing slash.
  • Google Cloud Storage: Ensure you uploaded the correct JSON service-account key file and that the service account has Storage Object Viewer privileges.
  • S3 and GCS paths are case-sensitive. Verify the exact spelling and capitalization of bucket folder names.
  • Files with unsupported extensions are skipped automatically. Ensure your images are .jpg, .jpeg, .png, or .tiff.
  • Ask Claude: “What was the error for the Shelf Images import?”
  • Claude reads the error attribute from get_job_status. Correct the root cause (typically IAM permissions or incorrect bucket name) and re-trigger the import.

MCP Tools Reference

Inspect inputs and outputs for dataset_create, connect_cloud_source, and list_connections.

MCP Workflows

See end-to-end workflows chaining cloud imports with project creation and exports.

AWS S3 Setup Guide

Step-by-step AWS IAM user and bucket policy creation.

GCS Setup Guide

Step-by-step Google Cloud service account key configuration.