Skip to main content
Glama
MediaShareORG

YourImageShare

Official
README.md
# yourimageshare-mcp

[![npm version](https://img.shields.io/npm/v/yourimageshare-mcp.svg)](https://www.npmjs.com/package/yourimageshare-mcp)
[![npm downloads](https://img.shields.io/npm/dm/yourimageshare-mcp.svg)](https://www.npmjs.com/package/yourimageshare-mcp)
[![smithery badge](https://smithery.ai/badge/team-54m5/yourimageshare)](https://smithery.ai/servers/team-54m5/yourimageshare)
[![yourimageshare MCP server](https://glama.ai/mcp/servers/MediaShareORG/yourimageshare/badges/card.svg)](https://glama.ai/mcp/servers/MediaShareORG/yourimageshare)

MCP (Model Context Protocol) server for [YourImageShare](https://yourimageshare.com).
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.

- **Get an API key:** sign in and open the **API** tab at
  [yourimageshare.com/my-account](https://yourimageshare.com/my-account).
- **Full HTTP reference:** [yourimageshare.com/about/api](https://yourimageshare.com/about/api).
- **OpenAPI 3.1 spec:** [yourimageshare.com/openapi.json](https://yourimageshare.com/openapi.json),
  if your tooling prefers that to this README.

## Install / run

No install needed - run directly with `npx`:

```bash
npx yourimageshare-mcp
```

Also listed on [Smithery](https://smithery.ai/servers/team-54m5/yourimageshare), 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`):

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

## 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. 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`](https://www.npmjs.com/package/yourimageshare)
  npm package, so this server's releases aren't coupled to that package's.

## License

MIT

## Support

[yourimageshare.com/contact](https://yourimageshare.com/contact)

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

ActivityMaintained
ResponsivenessNo issues