MCP.so
ログイン

PicGo Uploader MCP Server

@veithly

PicGo Uploader MCP Server について

An MCP (Model Context Protocol) server that allows interaction with a running PicGo application to upload images.

基本情報

カテゴリ

その他

ライセンス

Apache-2.0 license

ランタイム

node

トランスポート

stdio

公開者

veithly

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "picgo-ipfs-uploader": {
      "command": "npx",
      "args": [
        "picgo-uploader"
      ],
      "disabled": false,
      "alwaysAllow": [
        "upload_image_via_picgo"
      ]
    }
  }
}

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is PicGo Uploader MCP Server?

An MCP server that connects to a running PicGo desktop application to upload images. It exposes PicGo’s image uploading capabilities as an MCP tool, allowing AI assistants to upload local image files via PicGo’s built-in server.

How to use PicGo Uploader MCP Server?

Install globally with npm install -g picgo-uploader or yarn global add picgo-uploader, then run the picgo-uploader command. The server listens on stdio and provides the upload_image_via_picgo tool, which accepts an array of absolute image paths.

Key features of PicGo Uploader MCP Server

  • Uploads one or more images via PicGo’s built-in server.
  • Requires PicGo desktop application running with server enabled.
  • Default server address: http://127.0.0.1:36677.
  • Outputs uploaded image URLs as a JSON string.
  • Works on any OS supported by Node.js v18+.
  • Simple CLI setup with global npm/yarn installation.

Use cases of PicGo Uploader MCP Server

  • Upload screenshots taken during an AI assistant session.
  • Automatically upload local images to a configured image hosting service.
  • Integrate image uploading into MCP‑compatible AI workflows without manual file handling.

FAQ from PicGo Uploader MCP Server

What does this server do that PicGo alone doesn’t?

It provides a standardized MCP tool interface so AI assistants can invoke image uploads through PicGo, enabling automated, in‑context uploading without manual interaction.

What are the runtime requirements?

Node.js v18 or later, the PicGo desktop application installed and running, and the PicGo server enabled (default port 36677).

Where do uploaded images go?

The server does not store images; it relies on PicGo’s configured upload destination (e.g., cloud storage, image host). The URLs returned are provided by PicGo after a successful upload.

Are there any known limitations?

The server only supports absolute file paths accessible on the machine where it runs. It cannot handle relative paths or files from other devices.

How does authentication or transport work?

Transport is stdio. No authentication is required; the server assumes a local, trusted environment where the PicGo server is already accessible.

コメント

「その他」の他のコンテンツ