Clipboard History Searcher MCP. Search URLs, code, and numbers from old clips.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Clipboard History Searcher. Find any URL, phone number, or code snippet you copied days ago. This MCP indexes your exported clipboard history (Ditto, CopyQ, Maccy) and lets your AI client search it like a database.
Stop losing data in your local history files; search it instantly.
What your AI agents can do
Search clipboard history
Parses an exported clipboard history file (JSON or TXT from Ditto, CopyQ, Maccy) and makes it searchable by your AI.
Parses an exported clipboard history file (JSON or TXT) and indexes it, allowing your AI client to find specific data like URLs, numbers, or code snippets.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Clipboard History Searcher: 1 Tool for History Parsing
Use the single tool to parse exported JSON and text clipboard history files, making all your past copied data searchable by your AI agent.
019e3878search clipboard history
Parses an exported clipboard history file (JSON or TXT from Ditto, CopyQ, Maccy) and makes it searchable by your AI.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Clipboard History Searcher, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
You ever lose something you copied days ago? Like a client's number, a specific URL, or a chunk of code? It happens to everyone. You use a clipboard manager—Ditto, CopyQ, Maccy—and you end up with this massive history file that's a nightmare to search manually.
This MCP indexes your exported clipboard history, making it instantly searchable by your AI client. You don't have to dig through local files; you just ask for it, and it shows up.
search_clipboard_history parses your exported clipboard history file (JSON or TXT from Ditto, CopyQ, Maccy) and makes it searchable by your AI. You feed it the history file, and your agent treats it like a proper database. You send a natural language query, and the tool searches the indexed history, giving you the relevant entry and its original timestamp.
It handles JSON exports (CopyQ, Maccy) and plain text (Ditto) so you don't have to worry about the file type. The tool limits output to 200 clips, which keeps your context window clean when you're sifting through huge histories. It doesn't need any outside dependencies; it's just native parsing of the file format itself.
How Clipboard History Searcher MCP Works
- 1 You point your AI client at the MCP, passing in your exported clipboard history file (JSON or TXT).
- 2 The
search_clipboard_historytool parses the file, indexing the content and metadata. - 3 Your AI client runs a query (e.g., 'find the URL with domain X') and receives the matched clip and its entry number.
The bottom line is, you treat your local clipboard history like a searchable database through your AI client.
Who Is Clipboard History Searcher MCP For?
The overworked developer who constantly needs to find a snippet they copied weeks ago. The technical writer who loses critical citations in their history file. The data analyst who needs a specific ID or formatted number from old logs. If your job requires you to 'find that thing you copied last week,' this is for you.
Needs to find a specific function signature or API endpoint that was copied and pasted into a temporary chat window weeks ago.
Needs to locate a precise citation, code block, or URL from a meeting's shared screen that's buried deep in their clipboard manager's history.
Needs to retrieve a client's phone number or account ID that was quickly exchanged during a call and logged in the clipboard history.
What Changes When You Connect
- Stop losing time manually scrolling through your clipboard history. The
search_clipboard_historytool indexes your entire export, letting your agent find data instantly. - The tool handles multiple formats: it reads JSON (CopyQ, Maccy) and plain text (Ditto) exports, so you don't need to worry about file type compatibility.
- You can search for specific data types. For instance, ask your agent to 'find all phone numbers' or 'show me code snippets' to filter the history immediately.
- Context overflow isn't a problem. The system is token-safe, showing up to 200 clips, which keeps your AI conversation clean and focused.
- Your AI agent processes the search using natural language. You don't need to learn complex query syntax; just ask it what you need.
- It's a pure parsing utility. It only reads the exported file; no dependencies or external writes are involved.
Real-World Use Cases
Finding an old API endpoint
A developer remembers a specific API endpoint but can't find it. They feed the history into the MCP and ask the agent: 'Show me any endpoint containing /v2/user.' The agent uses search_clipboard_history and returns the exact line, including the clip's original entry number.
Tracking a client's number
A PM needs a client's number from a meeting held last month. They upload the history and prompt the agent: 'Find all US phone numbers.' The agent scans the history and returns a list of phone numbers and the clip's original source context.
Retrieving a forgotten code snippet
A technical writer needs a small block of code they copied for a documentation update. They use the MCP and prompt: 'What are the Python code snippets in my history?' The agent runs search_clipboard_history and filters for code, saving them from manual searching.
Sifting through mixed content logs
A data analyst has a massive log of copied items (URLs, IDs, text). Instead of reading everything, they ask the agent: 'Give me all the URLs copied in the last week that contain 'vinkius'.' The agent uses search_clipboard_history to filter the noise and provide a clean list.
The Tradeoffs
Trying to read clipboard live
Writing a script that tries to interact with the operating system clipboard directly within a browser environment. This fails due to security restrictions, or it causes the script to crash and hang the page.
→
Export your history first (Ditto, CopyQ, Maccy). Then, connect the exported file to the Clipboard History Searcher MCP and use the search_clipboard_history tool to query it safely.
Using generic search tools
Relying on a file system search (like Windows Search) on the raw history file. These tools don't understand the context of what a 'clip' is, and they can't distinguish between a URL and plain text reliably.
→
Use the dedicated search_clipboard_history tool. It's built to parse the specific formats (JSON/TXT) used by clipboard managers, giving you accurate, contextual results.
Manual copy-pasting of history
Copying thousands of lines of history into a single text document and pasting it into the chat prompt. This exceeds context limits, makes the prompt huge, and slows down the AI response drastically.
→
Pass the exported file to the MCP, then invoke search_clipboard_history. The tool handles the parsing and querying efficiently, keeping the context small and focused.
When It Fits, When It Doesn't
Use this if your primary need is to search historical, non-live data copied to your local clipboard. You need to query files exported from managers like Ditto, CopyQ, or Maccy. It's ideal for finding specific data types (phone numbers, code, URLs) across large archives.
Don't use it if:
* You need to monitor the clipboard right now (you need a live hook).
* You are trying to search unstructured data outside of the clipboard (e.g., a PDF or a webpage). In those cases, you'd use a general document parsing tool.
* You are looking for general system logs or application data. You need the specific, formatted output of a clipboard manager's export.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by clipboard-native. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 1 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Finding that one piece of data copied weeks ago is a huge time sink.
Think about it. You copied a URL in a Slack thread, then a code snippet in a terminal, and finally a phone number in an email. Your clipboard manager saves all three, but finding that specific URL three weeks later means scrolling through hundreds of entries, trying to remember if it was in a JSON or TXT file, and manually copy-pasting it into a search bar.
With the Clipboard History Searcher MCP, you just upload the exported file. Your agent runs `search_clipboard_history` and surfaces the exact URL, complete with its original entry number. You get the data, not a list of where to look.
Clipboard History Searcher MCP Server: Search copied data instantly
No more opening multiple apps—the clipboard manager, the file viewer, and the search engine. You just connect the MCP. The tool handles the format differences (JSON vs. plain text) and the complex parsing logic. You simply ask your agent, 'What was the code snippet I copied on Tuesday?'
It's a direct, single-step process. You stop wasting time trying to remember the format or the file location. You get the answer directly from your chat interface.
Common Questions About Clipboard History Searcher MCP
How does the Clipboard History Searcher MCP Server work? +
The server indexes your exported history file (JSON or TXT). Your AI client queries this index using natural language, and the tool returns the specific data point and its original entry number.
Can I search for phone numbers using the Clipboard History Searcher MCP Server? +
Yes. The tool parses all text content, allowing you to ask the agent to filter for specific patterns like phone numbers, credit cards, or email addresses.
Does the Clipboard History Searcher MCP Server handle all clipboard managers? +
It handles the standard exports from major managers like Ditto, CopyQ, and Maccy, supporting both JSON and plain text formats.
Is the Clipboard History Searcher MCP Server limited by context window size? +
No. The tool is token-safe and limits the output to 200 clips, preventing context overflow while still providing a rich set of search results.
How does the `search_clipboard_history` tool handle different file formats in the Clipboard History Searcher MCP Server? +
It handles both JSON and plain text formats. You just point the tool at the exported history file, and the MCP handles the parsing automatically.
What is the maximum amount of data the Clipboard History Searcher MCP Server can index? +
The tool shows up to 200 clips. This limit prevents context overflow and keeps your AI client focused on the most relevant history entries.
Does the Clipboard History Searcher MCP Server support reading historical data from multiple clipboard managers? +
Yes, it supports managers like Ditto, CopyQ, and Maccy. As long as you export the history, the MCP can read the resulting JSON or TXT file.
Does the Clipboard History Searcher MCP Server require any special authentication or setup? +
No, it's designed for zero dependencies and pure native parsing. You only need the exported history file to start using the search_clipboard_history tool.
Which clipboard managers are supported? +
Any manager that exports as JSON or plain text: Ditto (Windows), CopyQ (cross-platform), Maccy (macOS), Clipy (macOS).
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.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Anthropic Alternative
Access Claude models via Anthropic API — send messages, count tokens, manage batches and discover models from any AI agent.
Refiner
Survey your SaaS users with in-app micro-surveys that capture NPS, feature feedback, and churn signals at the perfect moment.
Wrike
Collaborative project management to manage tasks, projects, and team workflows with AI.
You might also like
USDA FoodData Central Alternative
Manage your nutritional research — audit food records and nutrient data via AI.
Adrecord
Affiliate marketing network — manage programs, track transactions, and audit earnings via AI.
Veraset
Equip your agent to seamlessly query Veraset's mobility datasets. Run geospatial SQL, extract insights, and manage S3 buckets.