Schnellstart: Senden Sie den folgenden Prompt an Ihren Coding Agent:
请从 https://github.com/timerring/PicGo-MCP 安装并配置 PicGo MCP Server。
Ein MCP-stdio-Server, der PicGo Core direkt in den Prozess einbettet. Er ermöglicht es MCP-Clients wie Codex und Claude Desktop, vorhandene PicGo-Bildhost-Konfigurationen wiederzuverwenden – ohne dass die PicGo-Desktop-Anwendung ausgeführt werden muss und ohne Umweg über 127.0.0.1:36677.
Direkter Aufruf von PicGo Core 3, keine Abhängigkeit vom Desktop-Client.
Unterstützt lokale Dateien, file://-URLs und HTTP(S)-Bild-URLs.
Unterstützt Einzelbild- und Stapel-Uploads mit bis zu 20 Bildern.
Automatische Erkennung von PicGo-Desktop-, PicGo-Core- und CLI-Konfigurationen.
Unterstützt benutzerdefinierte Upload-Dateinamen und Rückgabeformate.
Gleichzeitige Aufrufe werden automatisch in eine Warteschlange gestellt, um die variablen PicGo-Upload-Zustände nicht gegenseitig zu verunreinigen.
Statustools geben keine Konfigurationswerte wie Token oder Geheimnisse zurück und zeigen das Benutzerverzeichnis als ~ an.
Related MCP server: flin-imgbb-mcp
Node.js >=20.19.0
Eine funktionierende PicGo-Konfigurationsdatei
Installation aus dem Quellcode:
npm install
npm run build
npm install -g .Stellen Sie sicher, dass der Befehl verfügbar ist:
picgo-mcp --helpcodex mcp add picgo -- picgo-mcp
codex mcp get picgoNachhinzufügen des MCP-Servers eine neue Aufgabe starten oder den Client aktualisieren, damit die Werkzeugliste neu geladen wird.
Nach der globalen Installation kann die folgende stdio-Konfiguration verwendet werden:
{
"mcpServers": {
"picgo": {
"command": "picgo-mcp"
}
}
}Wenn eine Konfigurationsdatei explizit angegeben werden muss:
{
"mcpServers": {
"picgo": {
"command": "picgo-mcp",
"args": ["--config", "/path/to/picgo/config.json"]
}
}
}Sie können auch die Umgebungsvariable PICGO_CONFIG_PATHsetzen. --config hat dabei Priorität gegenüber der Umgebungsvariable und der automatischen Erkennung.
Standardmäßig wird in folgender Reihenfolge gesucht:
macOS: ~/Library/Application Support/picgo/data.json
Windows: %APPDATA%/picgo/data.json
Linux: $XDG_CONFIG_HOME/picgo/data.json oder ~/.config/picgo/data.json
Alle Plattformen: ~/.picgo/config.json
Das folgende Beispiel lädt Bilder in das Verzeichnis images/ des Repositorys hoch und liefert über js Delibr – also über jsDelivr – die CDN-Adresse zurück:
{
"picBed": {
"uploader": "github",
"current": "github",
"github": {
"repo": "OWNER/REPOSITORY",
"branch": "main",
"path": "images/",
"customUrl": "https://cdn.jsdelivr.net/gh/OWNER/REPOSITORY@main",
"token": "YOUR_GITHUB_TOKEN"
}
},
"picgoPlugins": {},
"settings": {
"picgoMcp": {
"uploadNameTemplate": "${dateTime}-${fileName}${extName}",
"outputFormat": "${url}"
}
}
}Der GitHub-Token benötigt Schreibrechte für das Zielrepo.Repository. Übergeben Sie den Token nicht mit Git, in Issues, Protokolle oder Chats bezeichnet und beschränken Sie die Berechtigungen der Konfigurationsdatei auf den aktuellen Benutzer:
chmod 600 ~/.picgo/config.jsonPicGo Core 3 kann beim ersten Lesen von älteren Konfigurationen die uploader-Konfiguration und interne Winkeldaten ergänzen – das ist eine normale automatische Migration.
Konfigurationsort:
{
"settings": {
"picgoMcp": {
"uploadNameTemplate": "${dateTime}-${fileName}${extName}"
}
}
}Unterstützte Variablen:
Variable | Beispiel | Beschreibung |
|
| Lokales Datum |
|
| Lokale Zeit mit Sekundengenauigkeit |
|
| Originaldateiname ohne Erweiterung |
|
| Originale Erweiterung |
|
| Nullbasierender Index beim Stapel-Upload; leer |
Empfohlen:
${dateTime}-${fileName}${extName}Die Verwendung nur mit ${dateTime}${extName} kann bei Bildern, die innerhalb derselben Sekunde hochgeladen werden, zu Namenskonflikten führen. Die Vorlage führt nur Whitelist-Platzhalterersetzungen aus, kein JavaScript, und es ist nicht möglich, zusätzliche Pfade wie ../ über den Dateinamen zu schreiben. Entfernte Verzeichnisse sollten über die path-Konfiguration des Uploaders festgelegt werden.
Konfigurationsort:
{
"settings": {
"picgoMcp": {
"outputFormat": "${url}"
}
}
}Unterstützte Variablen:
${url} – die Bild-URL nach dem Upload.
${uploadedName} – der Dateiname nach dem Upload, ohne Erweiterung.
Häufige Formate:
${url}
Die Tool-Antwort enthält immer Bildinformationen, URL-Array, Markdown und die via Vorlage zusammengestellte formattedOutput, sodass der Aufrufer je nach Bedarf Felder auswählen kann.
upload_imageLädt ein lokales oder entferntes Bild hoch:
{
"source": "/path/to/image.png"
}upload_imagesLädt 1–20 Bilder im Massen-Upload hoch:
{
"sources": [
"/path/to/first.png",
"https://example.com/second.jpg"
]
}get_picgo_statusLiefert zurück, ob die Datei vorhanden ist, die PicGo-Version, den aktuellen Uploader, die konfigurierten Feldnamen sowie die verfügbaren Uploader. Dieses Tool gibt sich nicht zu Datumswerten noch Hochladen-Berechtigungen zurück.
{
"images": [
{
"url": "https://cdn.example.com/images/2026-08-23-17-34-47-example.png",
"fileName": "2026-08-23-17-34-47-example.png",
"width": 800,
"height": 600,
"size": 123456
}
],
"urls": [
"https://cdn.example.com/images/2026-08-23-17-34-47-example.png"
],
"markdown": "",
"formattedOutput": "https://cdn.example.com/images/2026-08-23-17-34-47-example.png"
}MCP-Clients starten in der Regel einen picgo-mcp-stdio-Prozess und verwenden ihn für die Dauer der Client-Sitzung erneut. Nur wenn ein Upload-Tool (Upload-Werkzeug) aufgerufen wird, werden Bilder gelesen und die Bildquelle sowie das Bildhostservice aufgerufen; Danach, wenn der Client die Verbindung oft schließt, beendet sich der Serverprozess und gibt Speicher frei.
PicGo hält einen veränderlichen Ein- und Ausgabezustand; daher dieses Projekt wird gleichzeitige Uploadanfragen seriell aus.
Keine Tokens in Befehlsparametern angeben; Zugangsdaten sollten aus der PicGo-Konfiguration verwaltet werden.
MCP-Tools geben keine Zugangsdaten weiter; Statustools liefern nur Feldnamen.
Der Pfpour das Home-Verzeichnis wird in Tool-Antworten als ~ angezeigt.
HTTP(S)-Bilder werden zuerst von PicGo heruntergeladen und danach in den konfigurierten Bildhost hochgeladen.
PicGo lädt Plugins gemäß der Konfiguration– laden Sie nur vertrauenswürdige und aktivieren Sie diese.
Kann den stdio-Server nicht zu nicht vertrauenswürdige Clients bekannt.
Picugo 3.0.1-Abhangigkeitsbaum enthält derzeit noch npm-Sicherheitabschränkungen zu image-size und alten inquirer/tmp. Der te erstere kann bei speziell präparierten Bildern zu Denial-of-Service-Prozessen führen; Letztere liegt im Pfad der PicGo-CLI-Interaktion, die von diesem Projekt nicht aufgerufen wird. Diese Abhängigkeiten müssen durch das PicGo-Upstream aktualisiert werden.
npm install
npm test
npm run check
npm run buildDie Tests decken derzeit Konfigurationserkennung, Registrierung der MCP-Tools, Statusschwärzung, Upload-Eingabevalidierung, Namevorlagen, Ausgabevorlagen und Datenschutzprüfung für veröffentlichte Dateien ab.
Show the selected config path, PicGo version, active uploader, configured field names, and available uploaders. Secret values are never returned.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish read-only, idempotent, non-destructive behavior. The description adds valuable context by explicitly noting that secret values are never returned, which informs the agent about a meaningful privacy guarantee beyond the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One sentence, front-loaded with the primary output items, and ends with an important caveat about secrets. Every part contributes value with no repetition or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter, read-only status tool with rich annotations and no output schema, the description fully covers what an agent needs to understand its behavior and call it correctly. No missing information is significant.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are no parameters, so the schema already fully communicates invocation requirements. The description has nothing to add about parameter semantics, and the baseline of 4 is appropriate for a zero-parameter tool.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description begins with 'Show' and names a concrete set of outputs (config path, version, active uploader, field names, available uploaders). It clearly distinguishes this inspection tool from the sibling upload tools by framing it as read-only status retrieval.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies this tool is for inspecting current PicGo configuration state rather than performing uploads. It does not explicitly state 'use this before uploading' or name alternatives, but the read-only nature and content list make the intended context clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Upload one local image file or HTTP(S) image URL using the active PicGo uploader.
| Name | Required | Description | Default |
|---|---|---|---|
| source | Yes | Local file path, file:// URL, or HTTP(S) image URL |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=false and idempotentHint=false, which the description does not contradict. The description offers one extra context point: it depends on the 'active' PicGo uploader, implying configuration prerequisites. It does not explain side effects, failures, or response behavior, but the annotation coverage reduces the burden.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One short, direct sentence captures the entire behavior with the key constraint 'one' placed up front. There is no filler or redundant wording.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has one well-documented parameter and annotations cover mutability, idempotency, and safety, the description is nearly complete for a simple upload call. It could optionally mention what happens upon success or failure, but that is likely redundant for such a niche tool. The 'active PicGo uploader' hints at a real precondition that could be missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% since the single parameter 'source' is fully documented as a local file path, file:// URL, or HTTP(S) image URL. The description mostly echoes the same semantics without adding format validations, constraints, or examples. Essentially the full burden is handled by the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: 'Upload one local image file or HTTP(S) image URL using the active PicGo uploader.' The word 'one' clearly distinguishes it from the plural sibling tool upload_images. The title reinforces purpose without ambiguity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The singular 'one' implicitly contrasts with the plural upload_images sibling, giving a subtle cue. However, the description never explicitly states when to use this tool vs upload_images or get_picgo_status, nor any exclusion conditions. Guidance is implied rather than clearly stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Upload up to 20 local image files or HTTP(S) image URLs in one PicGo batch.
| Name | Required | Description | Default |
|---|---|---|---|
| sources | Yes | Local file paths, file:// URLs, or HTTP(S) image URLs |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly=false, idempotent=false, and destructive=false. The description adds that the operation is a batched upload accepting files or URLs, but it does not disclose side effects such as duplicate uploads on repeated calls or how partial failures are handled. This is modest added context beyond annotations, but not comprehensive.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence captures the action, accepted inputs, count limit, and batching model. It is front-loaded and every phrase earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter tool, the definition is sufficient to understand what to pass and why this tool is relevant. The only meaningful gaps are the absence of an explicit mention of the singular sibling and no description of return values or error behavior, but these are minor given the tool's simplicity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the description mostly restates the schema's own information: local paths, file:// URLs, HTTP(S) URLs, and the 20-item limit. It confirms the parameter's meaning but does not add meaningful detail beyond the schema, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific action verb and resource: uploading local image files or HTTP(S) image URLs. It also specifies the batch boundary of up to 20, which clearly differentiates this tool from the singular sibling upload_image.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'in one PicGo batch' plus 'up to 20' clearly establishes this is the tool for multiple-image uploads. It does not explicitly name upload_image for the single-image case or explain when to use get_picgo_status, but the usage context is strongly implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v0.1.0get_picgo_statusupload_imageupload_imagesScored across 3 tools
upload_image and upload_images are clearly differentiated as singular vs. batch operations, and get_picgo_status serves a distinct diagnostic purpose. No tools overlap in a way that would cause selection confusion.
All tool names follow the same snake_case verb_noun pattern: upload_image, upload_images, get_picgo_status. The naming is predictable and consistent across the set.
Three tools is on the smaller side but well-suited for a focused image-upload server. Each tool provides a distinct needed capability: single upload, batch upload, and status/configuration inspection.
The server covers the core upload lifecycle well, including single and batch uploads plus status/uploader information. A minor gap is the lack of an explicit uploader-selection or configuration tool, but the active uploader is readable via status, so agents can work around it.
MCP server for OpenAI API (chat completions, image generation, embeddings) via AceDataCloud
Convert images to PNG, JPEG, WebP, or AVIF through one public remote MCP tool.
Image processing over MCP: compress and split images, generate images and QR codes.
MCP server for Qwen Image 3 AI image generation