Image Annotate MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Human-in-the-loop image annotation. Open a session with annotate_image, the user draws boxes / points / polygons in a local web page, then annotate_wait blocks until they hit save and returns pixel coordinates, names and cropped templates. annotate_wait blocking for a while is normal, not a hang.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| annotate_imageA | Open an annotation session for one or more images and return a localhost URL. The user opens that URL and draws boxes (templates), points (click targets) or free-form polygons joined by straight segments, names them, then hits 保存. Then call annotate_wait to collect the result. source: local file path | data URL | raw base64 | 'screen' (live screen capture) | a list of any of those for a multi-image session. Omit it to capture the screen. resize_to: optional [width, height]; by default the image is NOT resampled, so coordinates always match the original file. |
| annotate_waitA | Block until the user saves the annotation (or the timeout fires), then return the annotations: per image, a list of {index, name, type, box|point|points, template, hidden?}. A status of 'pending' means the user has not saved yet -- that is NOT an error, just call annotate_wait again. Pass since_rev to only wait for saves newer than what you already have. Keep timeout_s below your MCP client's own tool timeout. |
| annotate_statusB | Non-blocking status of one session: pending / saved / cancelled, current rev, how many items so far, and how long it has been open. |
| annotate_cancelA | Close a session and its local web server. Anyone blocked in annotate_wait wakes up as cancelled. |
| annotate_listB | List annotations saved on disk, newest first. |
| annotate_loadA | Load one saved annotation by name (or file path) and return the full structured payload: schema 2 with images[] -> items[] and template filenames. |
| annotate_exportA | Export a saved annotation. fmt='png' renders the base image with numbered outlines (for a multimodal agent to look at), 'py' emits coordinate constants plus a template map, 'json' / 'yaml' dump the payload. Returns file paths and, for 'py', the generated source. |
| annotate_renderA | Render the numbered annotation picture for one saved annotation and return it as image content, so you can read the labels yourself instead of asking the user to type names. Needs annotate_export(fmt='png') to have been run first, or it will render on the fly. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool maps to a distinct phase of the annotation lifecycle: open session, block, poll, cancel, list, load, export, render. The only real overlap is annotate_export(fmt='png') versus annotate_render, both of which produce the numbered outline image, and the descriptions explicitly note the render-on-the-fly fallback, so the boundary is workable though slightly blurry.
All eight tools share a consistent snake_case 'annotate_' prefix, which makes the set easy to scan. Minor deviation: some suffixes are verbs (load, wait, cancel, list, export, render) while others are nouns (image, status), so the verb_noun pattern isn't perfectly uniform.
Eight tools is well-scoped for an interactive annotation server: session open/wait/status/cancel, persistence via list/load, and output via export/render. No tool looks redundant or bolted on.
The session lifecycle and persistence read path are fully covered, including a non-blocking status escape hatch and multiple export formats. Gaps are minor: there is no delete, rename, or update operation for saved annotations, so housekeeping of accumulated files must happen outside the tool surface.