← Registry

Productivity

whenmeet.me

Helps schedule meetings by aggregating availability from calendars and managing events.

1 endpoint8 known toolsFirst detected June 17, 2026Last detected August 29, 2026

ENDPOINT 1

https://whenmeet.me/mcp

No auth detected

MCP server metadata

Name
WhenMeet.me
Version
1.0.0
Capabilities
tools
Server instructions

WhenMeet.me finds a meeting time that works for everyone across companies and calendar providers (Google Calendar, Microsoft Outlook; others mark free time by hand). Typical flow: 1. find_common_slots with the participants' emails → ranked times when everyone is free (requires auth; data sources per participant are reported as self/manual/host). Each participant is filtered and scored in their OWN timezone; when no everyone-free time exists the ranker still returns the best "compromise" slots (allFree:false). 2. create_meeting with the chosen slot → calendar event + Meet/Teams link + share URL (/m/<id>) that invitees receive by email. 3. Anyone with the share URL can get_meeting, get_meeting_availability (aggregated group heat-map) and suggest_time; the host uses respond_to_suggestion to accept (moves the event) or decline. 4. set_manual_availability publishes hand-marked free slots for people without a connectable calendar (e.g. Apple iCloud). Authenticated tools need "Authorization: Bearer mn_…" — create a token at POST /api/tokens while signed in. Times are unix milliseconds; tz is an IANA zone name.

Known tools 8

find_common_slots

Rank the best meeting times for the given participants, merging live Google/Microsoft calendar data, hand-marked availability and the heat-map sources.

Inferred read-only
create_meeting

Confirm a meeting: writes the event into the authenticated host’s calendar with an optional Google Meet/Teams link, emails invites with an ICS attachment, and returns the share URL (/m/<id>).

Inferred read-only
get_meeting

Read a meeting by its share-link id (the UUID from /m/<id>): time, title, conference URL, host, and any proposed alternate times with their status.

Inferred read-only
get_meeting_availability

Aggregated group availability for an existing meeting (the symmetric heat-map): per-30-min-slot counts of how many participants are free, plus ranked slots (per-participant timezones, buffer + soonness scoring, allFree:true everyone-free slots and allFree:false compromise slots).

Inferred read-only
suggest_time

Propose a different time for an existing meeting on behalf of a guest.

Inferred read-only
respond_to_suggestion

Accept or decline a proposed alternate time.

Inferred read-only
set_manual_availability

Publish hand-marked FREE time slots for an email address (the no-calendar fallback, e.

Potential side effects
get_manual_availability

Read previously hand-marked free slots for an email within a window.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.whenmeet-me]
url = "https://whenmeet.me/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "whenmeet-me": {
      "type": "http",
      "url": "https://whenmeet.me/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: whenmeet-me
Remote MCP URL: https://whenmeet.me/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "whenmeet-me": {
      "url": "https://whenmeet.me/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "whenmeet-me": {
      "type": "http",
      "url": "https://whenmeet.me/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "whenmeet-me",
  "transport": "streamable-http",
  "url": "https://whenmeet.me/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for whenmeet.me was fetched 2026-08-20T03:06:22.707Z and is being refreshed.

Trust status Trusted

whenmeet.me is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.