Skip to main content
Glama
YourImageShare

YourImageShare

Official

yourimageshare-mcp

npm version npm downloads yourimageshare MCP server

MCP (Model Context Protocol) server for YourImageShare. Built for AI coding agents (Claude Code, Cursor, and other MCP-compatible tools) - paste a screenshot into a bug report, a PR description, or a support thread as a real URL instead of a base64 blob or a manual upload step. Works the same way with Claude Desktop and any other MCP client.

Install / run

No install needed - run directly with npx:

npx yourimageshare-mcp

Also listed on Smithery, if your MCP client installs from there instead.

Claude Desktop / Claude Code config

Add to your MCP client's config (e.g. claude_desktop_config.json):

{
  "mcpServers": {
    "yourimageshare": {
      "command": "npx",
      "args": ["-y", "yourimageshare-mcp"],
      "env": {
        "YIS_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

Related MCP server: uploadthing-mcp

Environment variables

Variable

Required

Purpose

YIS_API_KEY

yes

Your YourImageShare API key.

YIS_BASE_URL

no

Override the API base URL (default https://yourimageshare.com/api). For testing only.

Tools

upload_image

Upload a file (up to 200 MB - files over 90 MB are sent in pieces automatically). Provide exactly one of:

  • path - a local file path this server process can read,

  • base64 + filename - inline file contents, for MCP clients with no local filesystem access, or

  • url - a public http(s) link the YourImageShare server downloads itself.

Optional expiresIn (seconds, 60 to 2,592,000 = 30 days) auto-deletes the upload later. If the account already uploaded this exact file, the existing upload is returned with duplicate: true; set allowDuplicate to store a new copy. Returns id, type, path, src, direct, thumb (280 px WebP thumbnail), width, height, size, locked, expires_at and duplicate - store src, since path can change after conversion.

Also optional: visibility (unlisted by default - file and page for anyone with the link; private - file only, no page for others; public - listed), title (90 characters) and description (500). New uploads return a one-time delete_url.

get_upload

Requires id. Returns that upload's links, thumbnail, size, visibility, title and description.

update_upload

Requires id, plus any of visibility, title, description. Only what you pass changes; an empty string clears a title or description.

list_uploads

Optional page (defaults to 1, 50 per page). Returns your uploads newest first.

delete_upload

Requires id (from upload_image/list_uploads). Permanently deletes the upload.

Notes

  • This server only ever acts as the account tied to YIS_API_KEY - there's no way for a connected agent to act as any other account.

  • Errors from the API (bad key, rate limit, file rejected by moderation, etc.) come back as a tool error result with the API's own message, not a crashed tool call.

  • Built as a small, self-contained client rather than depending on the separate yourimageshare npm package, so this server's releases aren't coupled to that package's.

License

MIT

Support

yourimageshare.com/contact

Available Tools

3 tools
delete_uploadDelete an uploadA
DestructiveIdempotent
Inspect

Permanently delete one of your YourImageShare uploads by id - irreversible, the file and its links stop working immediately. Get the id from upload_image's response right after uploading, or from list_uploads if you no longer have it. Errors (not found, already deleted, wrong owner) come back as a normal tool error.

NameRequiredDescriptionDefault
idYesThe upload id to delete (the `id` field returned by upload_image/list_uploads).

Output Schema

NameRequiredDescription
idYes
deletedYes
list_uploadsList your uploadsA
Read-onlyIdempotent
Inspect

List your YourImageShare uploads, newest first, 50 per page - use this to find an upload's id (needed by delete_upload) when you only have its URL or remember it by content, since there's no lookup-by-URL endpoint. Each result includes the same three link fields upload_image returns, plus title and created_at. An out-of-range page number returns an empty data array, not an error.

NameRequiredDescriptionDefault
pageNoPage number. Defaults to 1.

Output Schema

NameRequiredDescription
dataYes
metaYes
upload_imageUpload an image or videoAInspect

Upload an image or video to YourImageShare and get back a shareable link. Accepts JPG, PNG, GIF, WEBP, AVIF, BMP, TIFF, HEIC/HEIF images and MP4, WEBM, AVI video, 100KB-200MB. Provide path for a file on disk this server can read, or base64 + filename for in-memory content (e.g. no local filesystem access) - never both. Returns three different URLs for the same upload (see output fields): a raw storage link, a direct embeddable link, and a shareable page link - pick whichever fits where it's going. Errors (oversized/unsupported file, bad API key, rate limit) come back as a normal tool error, not a thrown exception.

NameRequiredDescriptionDefault
pathNoLocal file path to upload.
base64NoBase64-encoded file contents. Requires `filename`.
filenameNoFilename to use. Required with `base64`; inferred from `path` otherwise.
expiresInNoAuto-delete after this many seconds (60 to 2,592,000 = 30 days). Omit for a permanent upload.

Output Schema

NameRequiredDescription
idYesUnique identifier for this upload. Pass to delete_upload to remove it.
srcYesDirect/embeddable file URL - use this for <img>/<video> src attributes.
pathYesRaw storage URL - the literal file, e.g. i.yourimageshare.com/xxx.webp.
typeYes
directYesThe shareable page URL (title, description, comments, share buttons). Despite the field name, this is NOT a direct file link - use `src` for that.
expires_atYesISO 8601 auto-delete timestamp, or null if the upload never expires.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 3 tool updatesv1.0.6
    • First observeddelete_upload
    • First observedlist_uploads
    • First observedupload_image

TDQS

A4.7/5.0

Scored across 3 tools

Disambiguation5/5

The three tools have clearly distinct operations: upload creates a shareable upload, list enumerates existing uploads, and delete removes one by ID. There is no overlap or ambiguity in their purposes.

Naming Consistency5/5

All tools follow the same verb_noun pattern: upload_image, list_uploads, delete_upload. The minor singular/plural difference is not confusing and the naming style is consistent across the set.

Tool Count5/5

Three tools is well-scoped for a simple image-sharing server. Each tool covers a necessary core operation and no redundant tools are present.

Completeness5/5

The tool set covers the full lifecycle of a hosted upload: create via upload_image, read/search via list_uploads, and delete via delete_upload. There are no dead ends or missing core operations for this domain.

Maintenance

ActivityNo data
ResponsivenessOutdated data

Related MCP Connectors

Related MCP Servers