Which clipboard managers are supported?

This MCP supports Ditto, CopyQ, and Maccy.

What file formats can I use?

It can parse JSON exports used by CopyQ and Maccy, as well as plain text exports from Ditto.

Will this slow down my AI client?

No, the MCP is designed to be token-safe by limiting the output to the 200 most relevant clips.

Do I need to install extra software?

No, the MCP uses pure native parsing and requires no additional dependencies.

How do I get my history into the MCP?

You simply export your history from your clipboard manager and point your agent toward those files.

Does it capture images from clipboard?

No, this parser focuses on textual clipboard entries to save AI context tokens.

Is my clipboard data sent to the cloud?

No. Parsed locally. Only text entries are sent to AI context during your session.

An astronaut overseeing a futuristic data hub

Download PDF Markdown Version

Connect Clipboard History Searcher to ChatGPT and Claude

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Turn your exported clipboard history into a searchable knowledge base.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 1 capability

We ship only the actions that matter.

Capability set01 / 01

01

1 capability in this set.

Part of 1 available through Clipboard History Searcher.

01
Search clipboard history
This capability parses exported clipboard history files in JSON or plain text formats. It allows your AI to search through Ditto, CopyQ, or Maccy exports to find specific content.

Real work

What teams actually run

Code Retrieval

Find a specific function or variable name you copied an hour ago while refactoring.

Contact Recovery

Ask your agent to find a phone number or email address you copied during a meeting.

URL Hunting

Locate a specific documentation link you copied earlier in your research session.

Data Auditing

Have your agent list all the unique strings or IDs you have copied during a data migration task.

Automate a task

Put Clipboard History Searcher to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Clipboard History Searcher works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put Clipboard History Searcher to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

920ms average. Fast in production.

Clipboard History Searcher is checked daily against the live service.

Daily averagePeak 1083ms

Oct 3Today

Fastest day: 673ms
Slowest day: 1083ms
14-day trend: Improving-6%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 1 capability arrives ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Clipboard History Searcher, so you can see the experience inside your AI.

It does not authenticate your account with Clipboard History Searcher. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Clipboard History Searcher Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_DMMaILLFq773X6a6GyTPbXNQUISwvzxx1QMXczD9/mcp

Claude Desktop

Follow the steps below to connect in seconds.

1In Claude Desktop, open Settings → Connectors.
2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
3Click Add and start a new chat — Clipboard History Searcher capabilities are ready to use.

Configuration · claude_desktop_config.jsonCopy

{
  "mcpServers": {
    "clipboard-history-searcher-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_DMMaILLFq773X6a6GyTPbXNQUISwvzxx1QMXczD9/mcp"
    }
  }
}

Claude
ChatGPT
Cursor
VS Code
Windsurf
Claude Code
JetBrains
Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Clipboard History Searcher in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Clipboard History Searcher owners hand off.

This is for anyone who relies on clipboard managers to keep track of their work and wants to use an AI agent to retrieve that data.

01
Software Developers
They hand off the task of finding specific code snippets or configuration strings copied earlier in a session.
02
Data Researchers
They use the agent to pull specific URLs or data points they have collected throughout the day.
03
Administrative Professionals
They ask the agent to find contact information or addresses copied during heavy data entry tasks.

FAQ

Questions Clipboard History Searcher owners ask.

01
Which clipboard managers are supported?
This MCP supports Ditto, CopyQ, and Maccy.
02
What file formats can I use?
It can parse JSON exports used by CopyQ and Maccy, as well as plain text exports from Ditto.
03
Will this slow down my AI client?
No, the MCP is designed to be token-safe by limiting the output to the 200 most relevant clips.
04
Do I need to install extra software?
No, the MCP uses pure native parsing and requires no additional dependencies.
05
How do I get my history into the MCP?
You simply export your history from your clipboard manager and point your agent toward those files.
06
Does it capture images from clipboard?
No, this parser focuses on textual clipboard entries to save AI context tokens.
07
Is my clipboard data sent to the cloud?
No. Parsed locally. Only text entries are sent to AI context during your session.