Meetwhen MCP Server

dev.workers.perch-app.meetwhen/meetwhen

answering

Meetwhen is answering right now. Last checked 7 min ago. It exposes 2 tools.

Free no-signup group scheduling (a modern When2meet): share one link, find a time for everyone.

Uptime history 43 hours of history

43 hours agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

61 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 7 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add meetwhen --transport http https://meetwhen.perch-app.workers.dev/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "meetwhen": {
      "url": "https://meetwhen.perch-app.workers.dev/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.meetwhen]
url = "https://meetwhen.perch-app.workers.dev/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "meetwhen": {
      "url": "https://meetwhen.perch-app.workers.dev/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "meetwhen": {
      "url": "https://meetwhen.perch-app.workers.dev/mcp"
    }
  }
}

Available tools 2

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

event

create_event

Create a free, no-signup group-scheduling event (like When2meet) and get a shareable link. Give it candidate dates and a daily time window; it builds the availability grid. Send the returned url to everyone in the group — each person paints when they're free in their own timezone, and the best overlapping time surfaces automatically. Ideal when a user asks you to 'find a time' or 'set up a poll' for a meeting.

get_event

Read the current state of a meetwhen event: how many people responded, who, and the best overlapping time(s) so far. Use the event id returned by create_event (or found in a meetwhen /e/<id> URL).

Endpoints

URL	Transport	State	Latency	Checked
https://meetwhen.perch-app.workers.dev/mcp	streamable-http	answering	69 ms	7 min ago

Meetwhen — questions

Answers built from our own checks of this server.

What can Meetwhen do?

It exposes 2 tools, read directly from the server on our last check. Among them: create_event, get_event. 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 →

Is Meetwhen working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 61 ms. The bar chart above shows every period we have measured.

How do I connect Meetwhen?

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 Meetwhen need an API key?

No. Meetwhen completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Meetwhen?

It answers our handshake in 61 ms on average, which is faster than 96% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.