What can you do with this server?

This server allows you to upload images from your clipboard to Supabase Storage and manage file cleanup via MCP endpoints. * Upload Clipboard Images: Automatically upload images copied to the clipboard to Supabase Storage and return the public URL. * Cleanup Old Files: Manually trigger the deletion of files older than a specified number of days (default: 30 days). * MCP Integration: Expose clipboard functionality as MCP endpoints for AI agents. * Cross-Platform Support: Works on macOS, Windows, and Linux with platform-specific tools.

Which integrations are available for this server?

Can run as an Express HTTP server that exposes MCP endpoints via REST API for programmatic image uploading and file management. Provides platform-specific integration for clipboard monitoring on Linux using xclip (X11) or wl-paste (Wayland), with systemd for auto-start functionality. Provides platform-specific integration for clipboard monitoring and image capture on macOS using pngpaste, with LaunchAgents for auto-start functionality. Automatically uploads clipboard images to Supabase Storage and returns public URLs, with features for managing stored files including automatic cleanup of old files.

How do I use Clipboard to Supabase MCP Helper?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Clipboard to Supabase MCP Helper upload the image I just copied to my clipboard" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

de en es ja ko ru zh

Clipboard to Supabase MCP Helper

by martinbowling

Overview Schema Related Servers Score Discussions

TypeScript

Local

Clipboard to Supabase MCP Helper

A local agent that monitors the system clipboard, uploads any copied image to Supabase Storage, then writes the public (or signed) URL back to the clipboard.

Features

Zero-click image hosting: Copy an image, get a URL instantly
Low latency: Under 800ms from copy to URL
Cross-platform: Works on macOS, Windows, and Linux
MCP integration: Expose clipboard image upload as an MCP endpoint
Auto-start: Configure to run at system startup
Efficient detection: Hash-based deduplication with low CPU usage

Related MCP server: clipboard-vision-mcp

Prerequisites

Node.js 18+
Supabase account with Storage enabled
Platform-specific dependencies:
- macOS: pngpaste (brew install pngpaste)
- Windows/Linux: Native OS clipboard access

Installation

Clone the repository:

git clone https://github.com/martinbowling/clipboard-to-supabase-mcp-helper.git
cd clipboard-to-supabase-mcp-helper

Install dependencies:

npm install

Create a .env file based on .env.example:

SUPABASE_URL=https://<project>.supabase.co
SUPABASE_SERVICE_ROLE_KEY=your-service-role-key
BUCKET=media
MCP_PORT=3333

Test your Supabase connection:

npm run test:supabase

Build the project:

npm run build

Install as a system service:

For macOS:

npm run install:macos

For Linux:

npm run install:linux

For Windows:

npm run install:windows

Usage

Once installed and running, the helper will:

Monitor your clipboard for image changes (polling every 300ms)
Upload any copied images to your Supabase bucket
Place the public URL back in your clipboard, ready to paste

Running the Service

The clipboard helper can be run in two modes:

Stdio Mode (Default)

npm start

This runs the MCP server with StdioServerTransport, ideal for command-line usage.

HTTP Mode

npm run start:http

This runs an Express HTTP server on port 3333 (configurable) with a proper REST API endpoint.

MCP Integration

The helper exposes the following MCP endpoints:

Upload Clipboard Image

With HTTP server mode:

POST http://localhost:3333/mcp

Request body:

{
  "id": "1",
  "jsonrpc": "2.0",
  "method": "tool",
  "params": {
    "name": "upload_clipboard_image",
    "input": {}
  }
}

Response:

{
  "id": "1",
  "jsonrpc": "2.0",
  "result": {
    "content": [
      {
        "type": "text",
        "text": "https://your-project.supabase.co/storage/v1/object/public/media/clips/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.png"
      }
    ]
  }
}

Cleanup Old Files

The helper also provides an MCP endpoint to manually trigger cleanup of old files.

Request body:

{
  "id": "1",
  "jsonrpc": "2.0",
  "method": "tool",
  "params": {
    "name": "cleanup_old_files",
    "input": {
      "days": 30
    }
  }
}

Response:

{
  "id": "1",
  "jsonrpc": "2.0",
  "result": {
    "content": [
      {
        "type": "text",
        "text": "Cleanup completed: Deleted 5 files older than 30 days. Failed: 0."
      }
    ]
  }
}

The days parameter is optional. If not provided, it will use the value from the RETENTION_DAYS environment variable.

How It Works

Change Detection: Polls clipboard every 300ms and computes SHA-1 hash of image data
Deduplication: Only processes new or changed images based on hash comparison
Platform Adaptation: Uses platform-specific methods to capture clipboard images
Supabase Integration: Uploads images to your Supabase bucket with unique UUIDs
MCP Endpoint: Exposes functionality to AI agents via Model Context Protocol
Automatic Cleanup: Periodically removes images older than the configured retention period (default: 30 days)

Platform-Specific Notes

macOS

Requires pngpaste: Install with brew install pngpaste
Uses LaunchAgents for auto-start

Windows

Uses PowerShell's System.Windows.Forms.Clipboard for image capture
Uses Windows Registry for auto-start

Linux

Uses xclip (X11) or wl-paste (Wayland) for clipboard access
Uses systemd for auto-start

Development

# Run with live reload (stdio mode)
npm run dev

# Run with live reload (HTTP mode)
npm run dev:http

# Build for production
npm run build

# Run stdio version
npm start

# Run HTTP version
npm run start:http

License

MIT

Available Tools

2 tools

cleanup_old_filesD

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

upload_clipboard_imageD

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

D1.8/5.0

Disambiguation5/5

The two tools have clearly distinct purposes: cleanup_old_files handles file management, while upload_clipboard_image handles image uploads. There is no overlap in functionality, making them easy to distinguish.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern with snake_case naming: cleanup_old_files and upload_clipboard_image. The naming is predictable and uniform across the set.

Tool Count2/5

With only 2 tools, the server feels thin for a 'Clipboard to Supabase MCP Helper' that might imply broader clipboard or Supabase integration. This minimal set likely leaves gaps in functionality.

Completeness2/5

Inferred domain includes clipboard operations and Supabase integration, but the tools only cover image uploads and file cleanup. Missing obvious functions like handling text/data from clipboard or other Supabase CRUD operations.

Maintenance

ActivityInactive

ResponsivenessSyncing

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

pixelvault A
io.github.pixelvault-dev
Agent-first image hosting — upload images and get instant CDN URLs.
Cloud Storage Multimedia Processing
2
transfer A
com.83blue.upload
Free no-signup file transfer, handoff & scratchpad memory for AI agents. Share files by url.
Cloud Storage Agent Orchestration
41
NoClick
io.github.noclickapp
Build agents to automate any background task. Works with your ChatGPT/Claude subscription.
Autonomous Agents App Automation
1
Run402 A
com.run402
x402 pay-per-call infra for agents: $0.03 image generation, Postgres, auth, storage, functions.
Cloud Platforms Agent Orchestration Databases
4224

Related MCP Servers

Claude Paste MCP
App Automation Developer Tools Multimedia Processing
G3sparky
F
license
A
quality
D
maintenance
A Windows-native MCP server that enables users to paste images, Excel tables, rich text, and plain text directly into Claude via a dedicated popup interface. It supports multi-item management and format conversion to streamline sharing complex clipboard data with the model.
Updated 9 months ago (2025-11-23 17:26 UTC)
1
clipboard-vision-mcp
AI & Machine Learning Image & Video Processing
Capetlevrai
A
license
B
quality
D
maintenance
Enables text-only AI models to understand clipboard images by describing them through a vision model, eliminating manual file saving.
Updated 21 days ago (2026-08-14 07:05 UTC)
12
44
MIT
ClipMCP
Developer Tools Knowledge & Memory Search
susmetaa01
A
license
Not graded
quality
D
maintenance
A standalone clipboard history MCP server for macOS that monitors clipboard in real-time, stores history locally in SQLite, and exposes it to any MCP-compatible AI assistant.
Updated 5 months ago (2026-04-19 14:40 UTC)
5
MIT
openai-gpt-image-1-mcp
Image & Video Processing AI & Machine Learning
DevRico003
F
license
Not graded
quality
D
maintenance
Provides AI agents and coding assistants with image generation and editing capabilities using OpenAI's GPT-image-1 model, with support for local or Supabase storage.
Updated a year ago (2025-05-15 16:20 UTC)
3

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/martinbowling/clipboard-to-supabase-mcp-helper'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

Clipboard to Supabase MCP Helper

Features

Prerequisites

Installation

Usage

Running the Service

Stdio Mode (Default)

HTTP Mode

MCP Integration

Upload Clipboard Image

Cleanup Old Files

How It Works

Platform-Specific Notes

macOS

Windows

Linux

Development

License

Available Tools

TDQS

TDQS

TDQS

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

Claude Paste MCP

clipboard-vision-mcp

ClipMCP

openai-gpt-image-1-mcp

Latest Blog Posts

MCP directory API