Image Label MCP Server
Related Servers
Alternatives to Image Label MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables Claude to generate and edit images through a live-discovered model catalog, including masked edits and exact output sizes, with browser-based sign-in and cost-annotated saved results. It runs locally over stdio and stores images in a configurable directory.7MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding assistants without native vision to analyze screenshots, errors, UI designs, and documents through a unified image understanding tool backed by multiple vision model providers. Supports local files, remote URLs, Data URIs, OCR, multi-crop processing, and stdio or HTTP deployment for shared access.404 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to generate images, list available models, and view generation history over stdio, SSE, and Streamable HTTP transports.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to generate images with the Z-Image-Turbo text-to-image model, list available models, and browse past generation history. It exposes the same structured tools over stdio, SSE, and Streamable HTTP transports for consistent agent integration.-
- AlicenseNot gradedqualityCmaintenanceLets AI agents generate images and videos through a self-hosted studio connected to the user's own fal.ai, Kie.ai or Higgsfield API keys, with tools for exploring models, submitting image and video jobs, waiting on results and importing media from URLs. Runs over HTTP with bearer-token authentication, so agents such as Claude Code, Codex, Cursor or Claude Desktop can create and retrieve media while provider keys stay encrypted server-side.MIT
- AlicenseNot gradedqualityDmaintenanceA lightweight stdio MCP server that adds image understanding to AI coding assistants via a single tool that sends images to any OpenAI-compatible multimodal endpoint.MIT
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: list vs get for retrieval, update_metadata for metadata, add/replace/remove for annotation modification, upload for ingestion, and export for output. The three annotation mutation tools are explicitly differentiated by their append, replace-all, and remove-by-id behaviors.
All eight tools follow a consistent snake_case verb_noun pattern (list_images, get_image, update_image_metadata, add_annotations, replace_annotations, remove_annotations, upload_image, export_annotations). There are no mixed conventions or vague verbs.
Eight tools is well-scoped for an image labeling server, covering image retrieval, metadata updates, annotation lifecycle, upload, and export without bloat. Each tool earns its place in the core workflow.
The server covers image upload/list/get, metadata update, full annotation add/replace/remove, and export. A delete-image operation is missing, and category management is absent, but these are minor gaps for the stated annotation-focused purpose.