MCP server exposing the YourImageShare upload API (upload/list/delete) as tools for AI agents.
io.github.MediaShareORG/yourimageshare MCP Server
This MCP server exposes the YourImageShare upload API to AI agents as callable tools. It is intended to support actions such as upload, list, and delete, making media-hosting functionality available through Model Context Protocol.
🛠️ Key Features
MCP server for YourImageShare upload API
Tools correspond to upload/list/delete operations
Described as an API access layer for AI agents
🚀 Use Cases
Integrate image upload and management with agents
Support file-sharing and image-hosting workflows
Use as a media offload component alongside related platforms
⚡ Developer Benefits
Standardized access via Model Context Protocol (MCP)
Positioned for implementation in environments using REST API and common runtimes
⚠️ Limitations
Server details are limited to the upload API (upload/list/delete); other API capabilities are not shown in the provided data
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.
Override the API base URL (default https://yourimageshare.com/api). For testing only.
Tools
upload_image
Upload a file. Provide either:
path - a local file path this server process can read, or
base64 + filename - inline file contents, for MCP clients with no local
filesystem access.
Optional expiresIn (seconds, 60 to 2,592,000 = 30 days) auto-deletes the
upload later. Returns the same JSON shape as the HTTP API's upload response
(id, type, path, src, direct, expires_at).
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.