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
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago