mcpbeat

Clippy MCP Server

io.github.IDTitanium/clippy
answering

Clippy is answering right now. Last checked moments ago. It exposes 9 tools.

AI agents can Create rooms and store/retrieve text and images, and hand link to humans no sign-up.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 42 hours of history
42 hours agonow
100.0%
Uptime 24h
92 of 92 checks
9
Tools
read from the server
510 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add clippy --transport http https://useclippy.cc/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "clippy": {
      "url": "https://useclippy.cc/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.clippy]
url = "https://useclippy.cc/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "clippy": {
      "url": "https://useclippy.cc/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "clippy": {
      "url": "https://useclippy.cc/mcp"
    }
  }
}

Available tools 9

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

room
create-room-tool
Create a brand-new Clippy room and get back its 6-character code, a private owner_token, and a share URL. Use this when you want a fresh shared clipboard to push content to a user (hand them the URL) or to coordinate with other agents. Keep the owner_token private — it grants password control over the room.
room-status-tool
Check whether a Clippy room exists, whether it is password-protected, and how many items it holds — without reading the contents. Handy before deciding to read or write, or to confirm a code a user gave you is valid.
set-room-password-tool
Lock or unlock a Clippy room. Requires the room owner_token (returned by create-room). Pass a password to lock the room; pass an empty password to remove the lock. Only the owner can change this.
item
delete-item-tool
Delete a single item from a Clippy room by its item id (the `id` returned by store-item / list-items). Any images attached to the item are removed too. This cannot be undone.
update-item-tool
Edit the text of an existing item in a Clippy room, identified by its item id (the `id` field returned by store-item / list-items). Image bytes are immutable; this changes only the text.
store
store-image-tool
Post one or more images (PNG, JPEG, GIF, or WEBP) to a Clippy room so they appear on every device watching it, optionally with a text caption. Pass each image as a base64 string or a data: URI. The room is created if it does not exist. Subscribed devices get a push notification. Returns the stored item, including direct URLs to fetch each image.
store-item-tool
Post a piece of text to a Clippy room so it appears on every device and agent watching that room. The room is created automatically if it does not exist yet. Subscribed devices receive a push notification. This is how you "send" something to a user or leave a note for another agent. Returns the stored item.
clear
clear-room-tool
Delete ALL items in a Clippy room (and their images). Use with care — this wipes everything shared in the room and cannot be undone. The room itself continues to exist and can be reused.
items
list-items-tool
Read the items in a Clippy room (newest first). Use this to pick up text a user or another agent left for you, or to see what is currently in a shared room. Pass `since` (a millisecond timestamp from a previous call) to fetch only items added after that point. Image items include direct image URLs.

Endpoints

URLTransportStateLatencyChecked
https://useclippy.cc/mcp streamable-http answering 347 ms 0 min ago

Clippy — questions

Answers built from our own checks of this server.

What can Clippy do?
It exposes 9 tools, read directly from the server on our last check. Among them: clear-room-tool, create-room-tool, delete-item-tool, list-items-tool, room-status-tool, set-room-password-tool and 3 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Clippy mostly used for?
Its tools cluster around room, store and item. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Clippy working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 510 ms. The bar chart above shows every period we have measured.
Is Clippy still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Clippy?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Clippy need an API key?
No. Clippy completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 9 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Clippy?
It answers our handshake in 510 ms on average, which is faster than 22% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.