About PicGo Uploader MCP Server
PicGo Uploader MCP Server exposes the upload capability of a running PicGo application to MCP clients. It uploads one or more local image files and returns the resulting image URLs.
Key features
- 01Upload one or more local images
- 02Use a running PicGo application
- 03Return uploaded image URLs
Use cases
- 01Upload a local screenshot and get its URL
- 02Send multiple images to PicGo for upload
MCP support
The MCP server exposes the upload_image_via_picgo tool, which accepts local image paths and returns URLs supplied by PicGo.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
1Saved tool list · updated 3w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| image_paths | array | Yes | An array of absolute paths to the image files to upload. |
Details
From the project READMEPicGo Uploader MCP Server
An MCP (Model Context Protocol) server that allows interaction with a running PicGo application to upload images.
Overview
This server exposes PicGo's image uploading capabilities as an MCP tool. It connects to the PicGo application's built-in server (usually running on http://127.0.0.1:36677) and provides a tool to upload local image files.
Prerequisites
- Node.js: Ensure you have Node.js (v18 or later recommended) installed.
- PicGo Application: You need the PicGo desktop application installed and running.
- PicGo Server Enabled: In PicGo's settings (
PicGo 设置->设置Server), enable the server. The default port is36677. Make sure it's running. - NPM or Yarn: For installing the package.
Installation
npm install -g picgo-uploader
or
yarn global add picgo-uploader
This will install the MCP server globally and make the picgo-uploader command available.
Running the Server
Simply execute the command in your terminal:
picgo-uploader
The server will start and listen for MCP connections via stdio. You should see a message like:
PicGo Uploader MCP server running on stdio
Keep this terminal window open while you want to use the server.
Usage (MCP Tool)
Once the server is running and connected to your MCP client (like Roo Code), you can use the provided tool:
Tool: upload_image_via_picgo
- Description: Uploads one or more images using the running PicGo server application.
- Input Schema:
{ "type": "object", "properties": { "image_paths": { "type": "array", "items": { "type": "string" }, "description": "An array of absolute paths to the image files to upload." } }, "required": ["image_paths"] } - Output: On success, returns a JSON string containing the array of uploaded image URLs provided by PicGo. On failure, returns an error message.
Example (use_mcp_tool):
<use_mcp_tool>
<server_name>picgo-uploader</server_name>
<tool_name>upload_image_via_picgo</tool_name>
<arguments>
{
"image_paths": [
"C:\\Users\\YourUser\\Pictures\\screenshot1.png",
"/home/user/images/diagram.jpg"
]
}
</arguments>
</use_mcp_tool>
Note: Ensure the file paths provided in image_paths are absolute paths accessible from the machine where the picgo-uploader server is running.
Troubleshooting
- Error: "PicGo server request error: connect ECONNREFUSED 127.0.0.1:36677":
- Make sure the PicGo application is running.
- Verify that the PicGo server is enabled in its settings and running on the default port
36677.
- Error: "Image path does not exist: ":
- Double-check that the provided image path is correct and absolute.
- Ensure the file exists at the specified location on the machine running the
picgo-uploader.
- Error: "PicGo upload failed: ...":
- This indicates an error reported by PicGo itself (e.g., invalid configuration for the selected uploader, network issues). Check the PicGo application logs for more details.
Development
- Clone the repository.
- Install dependencies:
npm install - Build the code:
npm run build - Run in development:
node build/index.js - Watch for changes:
npm run watch(in a separate terminal)
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.