# Kompressr [Health: Active]

**Category:** 📂 File Systems  
**Repository:** https://github.com/kompressrcdn/clients  
**GitHub Stars:** 0  
**npm Downloads (last month):** 247  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/kompressr

## Description
Upload, optimize and manage files, wait for processing, and generate private delivery links.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "kompressr": {
    "command": "npx",
    "args": ["-y","@kompressr/mcp-server@2.0.3"],
    "env": {
      "KOMPRESSR_API_KEY": ""
    }
  }
}
```

**Requires environment variables:** `KOMPRESSR_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## 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:

```sh
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.

_Full upstream README: https://allmcps.com/mcp/kompressr/readme_