Label Studio MCP Server

Created By
HumanSignala year ago
Overview

what is Label Studio MCP Server?

Label Studio MCP Server is a Model Context Protocol (MCP) server that facilitates interaction with a Label Studio instance, allowing for programmatic management of labeling projects, tasks, and predictions through natural language or structured calls.

how to use Label Studio MCP Server?

To use the MCP Server, set up a running instance of Label Studio, obtain an API key, and configure the server with the necessary environment variables. You can then make requests to manage projects and tasks.

key features of Label Studio MCP Server?

  • Project Management: Create, update, and view Label Studio projects.
  • Task Management: Import tasks, list tasks, and retrieve task data.
  • Prediction Integration: Add model predictions to tasks.
  • SDK Integration: Utilizes the official label-studio-sdk for communication.

use cases of Label Studio MCP Server?

  1. Automating the creation and management of labeling projects.
  2. Importing and managing tasks for data labeling.
  3. Integrating model predictions into labeling workflows.

FAQ from Label Studio MCP Server?

  • Can I use this server without a running Label Studio instance?

No, a running Label Studio instance is required to use the MCP Server.

  • Is there a cost associated with using Label Studio MCP Server?

The server is open-source and free to use, but you need a Label Studio instance which may have its own costs.

  • How do I obtain an API key for Label Studio?

You can obtain an API key from your user account settings in Label Studio.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
HumanSignal
Star
5
Language
Python
License
Apache-2.0 license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago