PicGo Uploader MCP Server

Created By
veithlya year ago
An MCP (Model Context Protocol) server that allows interaction with a running PicGo application to upload images.
Overview

what is PicGo Uploader MCP Server?

PicGo Uploader MCP Server is a Model Context Protocol (MCP) server that facilitates interaction with the PicGo application for uploading images.

how to use PicGo Uploader MCP Server?

To use the server, ensure you have the PicGo application running, install the MCP server globally using npm or yarn, and then run the server command in your terminal.

key features of PicGo Uploader MCP Server?

  • Connects to the PicGo application to enable image uploads.
  • Supports multiple image uploads through a single command.
  • Provides error handling and troubleshooting guidance.

use cases of PicGo Uploader MCP Server?

  1. Uploading images from local storage to cloud services via PicGo.
  2. Integrating image upload functionality into other applications using MCP.
  3. Automating image uploads in development workflows.

FAQ from PicGo Uploader MCP Server?

  • What prerequisites are needed to run the server?

You need Node.js, the PicGo application, and the PicGo server enabled.

  • How do I troubleshoot connection errors?

Ensure the PicGo application is running and the server is enabled in its settings.

  • Can I upload multiple images at once?

Yes! You can upload multiple images by providing their absolute paths in the input schema.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
veithly
Star
0
Language
JavaScript
License
Apache-2.0 license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago