Credentials. Connecting cloud storage means giving Label Studio bucket credentials; use a key scoped to just the labeling bucket.
Who it is forA team lead coordinating several annotators across multiple datasets.
The problemPassing files around and merging labels from several people leads to lost and conflicting work.
The outcomeOne server where every annotation is tied to a user account, with multiple projects and cloud storage imports.
What you need first
- Docker, or Python 3.10 or later for the pip install
- Docker Compose for the production stack with Nginx and PostgreSQL
- Optional: a model server built with the Label Studio ML backend for pre-labeling
Steps
- From a checkout of the repo, run
docker-compose upto start Label Studio, Nginx and PostgreSQL - Open the app at localhost and have each annotator sign up so their annotations are tied to their account
- Create one project per dataset and import from files or cloud storage such as Amazon AWS S3 or Google Cloud Storage
- For local S3 testing, run
docker compose -f docker-compose.yml -f docker-compose.minio.yml up -d - Use the REST API to pull finished annotations into your training pipeline
Prompt for your agent
Deploy HumanSignal/label-studio with the Docker Compose stack on <server>, connect project <name> to my <S3 or GCS bucket>, and write a script that uses the REST API to export completed annotations nightly.
Caveat. If the server is reachable from the internet, put it behind HTTPS and restrict sign ups to your team.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for HumanSignal/label-studio and "Run a shared labeling server for a team"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer