Aiyogg_tinypng Mcp Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Aiyogg TinyPNG MCP Server?

Aiyogg TinyPNG MCP Server is a server application that allows users to compress images using the TinyPNG API, providing an efficient way to reduce image file sizes for web and application use.

how to use Aiyogg TinyPNG MCP Server?

To use the server, you need to install the necessary dependencies, configure the mcp.json file with your TinyPNG API key, and then run the server using either bun or node.

key features of Aiyogg TinyPNG MCP Server?

  • Compress local and remote images using the TinyPNG API.
  • Easy configuration through a JSON file.
  • Supports various output formats for compressed images.

use cases of Aiyogg TinyPNG MCP Server?

  1. Reducing the size of images for faster web page loading.
  2. Compressing images for mobile applications to save bandwidth.
  3. Automating image compression in development workflows.

FAQ from Aiyogg TinyPNG MCP Server?

  • What is the required API key for?

The API key is necessary to authenticate your requests to the TinyPNG service for image compression.

  • Can I compress images in bulk?

Yes, you can set up scripts to compress multiple images by calling the server with different image paths.

  • Is there a limit to the size of images I can compress?

Yes, TinyPNG has limitations on the size of images that can be compressed, which is typically around 5MB per image.

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

Recommend Servers

View All
Voyei

2 hours ago
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