MCP.so
ログイン
Z

Zipline MCP Server

@dorogoy

基本情報

カテゴリ

その他

トランスポート

stdio

作者

dorogoy

投稿者

Sergio Rael

Zipline MCP Server について

概要はまだありません

Zipline MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "zipline": {
      "command": "npx",
      "args": [
        "-y",
        "zipline-mcp"
      ],
      "environment": {
        "ZIPLINE_TOKEN": "<YOUR-TOKEN>",
        "ZIPLINE_ENDPOINT": "http://localhost:3000"
      }
    }
  }
}

Zipline MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

上のボタンで一時的なサンドボックスでこのサーバーを実行し、ツール一覧を取得できます。

概要

What is Zipline Mcp?

Zipline Mcp is an MCP (Model Context Protocol) server that enables AI clients (e.g., Claude Desktop) to upload files to a Zipline-compatible file hosting instance. It provides tools for uploading, validating, previewing upload commands, and listing previously uploaded files.

How to use Zipline Mcp?

Install globally via npm install -g zipline-mcp or locally as a project dependency. Then configure your MCP client (e.g., Claude Desktop) by adding the server with command: npx, args: ['-y', 'zipline-mcp'], and environment variables ZIPLINE_TOKEN (required) and ZIPLINE_ENDPOINT (default: http://localhost:3000).

Key features of Zipline Mcp

  • Upload files to a Zipline instance with support for multiple formats.
  • Validate files locally before uploading.
  • Preview upload commands without executing them.
  • Retrieve only the download URL after upload.
  • List and search user files stored on the Zipline server.
  • Support text/code and image file types (e.g., txt, md, json, png, jpg).
  • Enhanced upload options: deletes‑at, password, max‑views, and folder.

Use cases of Zipline Mcp

  • Upload code snippets or configurations from an AI assistant to a private Zipline server.
  • Validate file existence and type before sending to Zipline.
  • List and search previously uploaded files for reuse or sharing.
  • Create time‑limited, password‑protected, or single‑view file links.
  • Integrate file upload capabilities into MCP‑based workflows (e.g., Claude Desktop).

よくある質問

1

What environment variables are required?

`ZIPLINE_TOKEN` (your Zipline API token) and `ZIPLINE_ENDPOINT` (the URL of your Zipline server, defaults to `http://localhost:3000`).

2

What file types are supported?

Text/code: txt, md, gpx, html, json, xml, csv, js, css, py, sh, yaml, yml. Images: png, jpg, jpeg, gif, webp, svg, bmp, tiff, ico, heic, avif. This set can be overridden via `ALLOWED_EXTENSIONS`.

3

How are uploaded files named?

The `format` parameter (optional) controls naming: `random` (default), `uuid`, `date`, `name`, `gfycat` (alias for `random-words`), or `random-words`. Values are case‑insensitive.

4

Where are files stored and how is access secured?

Files are stored on the Zipline server you specify. The MCP server acts as a bridge; it never stores files. Secure connections with HTTPS are recommended. API tokens should be stored in environment variables, not config files.

5

What authentication/transport does the server use?

The MCP server authenticates with the Zipline API using the provided `ZIPLINE_TOKEN`. Communication is over HTTP(S). The MCP client communicates with the server via standard MCP tool calls.

コメント

「その他」の他のコンテンツ