Log inSubmit server
Kompressr logo

Kompressr

Upload, optimize, process, and deliver Kompressr files through an MCP-compatible AI agent.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Kompressr

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "kompressr": {
      "command": "npx",
      "args": [
        "-y",
        "@kompressr/mcp-server@2.0.3"
      ],
      "env": {
        "KOMPRESSR_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

Kompressr MCP server connects AI agents to Kompressr for uploading, optimizing, managing, and delivering files. It runs through the JavaScript MCP package with Node.js 22 and uses a Kompressr API key for authenticated operations. Agents can wait for asynchronous processing to finish before requesting delivery links, including private links. Reach for it when an agent needs backend file workflows without embedding the full SDK directly in an application.

Use cases

  • Upload images from an agent-managed workflow
  • Wait for files to finish processing before delivery
  • Generate private links for stored attachments
  • Manage files through a chatbot with scoped user access

Key features

  • File uploads through MCP
  • Kompressr file optimization
  • Processing-status recovery workflows
  • Private delivery-link generation
  • Scoped access for multi-user agents

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 6d ago via OSV.dev · @kompressr/mcp-server@2.0.3 (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads247Package downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Kompressr works

What Kompressr does

Kompressr exposes file operations to AI agents through the Model Context Protocol. The server connects to Kompressr, a service for storing, optimizing, and delivering files. An agent can submit an upload, manage stored files, wait for processing to complete, and create delivery links for files that should remain private.

The MCP package uses the JavaScript SDK's file behavior. That gives agent workflows the same upload, permission, and recovery model available to JavaScript applications. It is intended for server-side or trusted-agent use, where project and user credentials can be kept out of untrusted clients.

How it works

Configure an MCP client to launch the package with npx, then provide a Kompressr API key through the client environment. The agent invokes file capabilities over MCP, while the server makes authenticated requests to Kompressr. Upload acceptance and processing are separate stages: after an upload is accepted, the agent should retain its identifier and wait until the file is ready before sharing its delivery URL.

Private-file workflows can use delivery links generated for restricted content. Applications that serve multiple users can also use scoped keys when their Kompressr plan and project configuration support them. The repository includes a chatbot integration path for provisioning identities, binding tools to authenticated users, handling private attachments, and refreshing delivery links.

Setup and configuration

Create a Kompressr account and project, then obtain an API key from the project's API Keys area. Store that value as KOMPRESSR_API_KEY in the MCP client's environment rather than placing it in prompts or application source.

A typical MCP launch command is:

Terminal
npx -y @kompressr/mcp-server@latest

The server requires Node.js 22 or newer. Claude Desktop has a dedicated installation walkthrough, and other MCP clients can use their standard configuration for a local command-based server. The package can also be installed and tested from the clients repository during development.

Tools and capabilities

Available workflows cover the following operations:

  • Upload files to Kompressr.
  • Optimize files through Kompressr processing.
  • Manage stored files.
  • Wait for an accepted upload to become ready.
  • Generate delivery links for private files.
  • Support user-scoped access through scoped credentials where the account plan permits it.

The exact operations available to an agent depend on the configured key and its Kompressr permissions. Keep project and master credentials on trusted backends, and select a credential for the authenticated user before making requests.

Limitations and notes

The free trial includes a finite total allowance for image uploads shared across the API, SDKs, MCP, and dashboard; it does not renew monthly. Scoped per-user keys require a Platform/AI project and a plan that includes them, such as Growth, API, or Enterprise.

Uploads may remain in processing after the server accepts them. A workflow that immediately publishes a URL can therefore fail or expose an incomplete result; save the upload identifier and wait for readiness first. The MCP package is based on the JavaScript SDK and requires Node.js 22. Credentials should not be exposed to browsers, untrusted users, or prompts.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Kompressr

Kompressr is an MCP server that connects AI agents to Kompressr for uploading, optimizing, managing, and delivering files. Its main tools cover file uploads, processing waits, file management, and private delivery-link generation. It runs through the JavaScript package and authenticates requests with a Kompressr API key.

Install it by configuring your MCP client to run `npx -y @kompressr/mcp-server@latest` with Node.js 22 or newer. Set `KOMPRESSR_API_KEY` in the client environment, then use the client's normal setup for a local command-based MCP server.

Wait for processing by retaining the identifier returned when the upload is accepted and invoking the server's readiness workflow before sharing the file URL. An accepted upload may still be processing, so publishing a delivery link immediately is unsafe.

Yes, Kompressr can generate private delivery links for stored files. Keep project or master credentials on a trusted backend, and use a credential associated with the authenticated user when building a multi-user chatbot or agent workflow.

Related MCP servers

All in File Systems All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewKompressr AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/kompressr?style=directory)](https://allmcps.com/mcp/kompressr)
HTML Embed
<a href="https://allmcps.com/mcp/kompressr"><img src="https://allmcps.com/api/badge/kompressr?style=directory" alt="Kompressr on AllMCPs" /></a>