WhenMeet.me — group scheduling

me.whenmeetPublished by whenmeet.meOfficial publisherv1.1.0Updated Oct 24, 2026

Group meeting scheduler — rank times everyone's free across Google & Outlook, book Meet/Teams.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

A remote group scheduling server that lets an assistant rank times when everyone is free across Google and Outlook calendars and book Meet or Teams meetings.

What you can do
Find times when a group is mutually free across Google and Outlook calendars, ranked by availability. Book meetings with Google Meet or Microsoft Teams links. The manifest lists no individual tools, so exact operations are not documented; the described scope is group scheduling and booking.
When to use it
Useful when coordinating a meeting across several people with mixed Google and Outlook calendars and you want the assistant to propose the best shared slots and book one.
Requirements
A remote MCP endpoint at whenmeet.me over streamable HTTP. OAuth authentication is required, so the user must sign in and grant calendar access. No environment variables or headers are declared.
Before you install
OAuth grants access to the user's Google and Outlook calendar data, which is shared with a third-party service. Booking creates calendar events and may send invitations to attendees, so confirm times and attendees before booking.

Installation

In SourceWeft

  1. Open WhenMeet.me — group scheduling in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/me.whenmeet%2Fscheduler/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.1.0LatestOct 17, 2026
  2. v1.0.0Sep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.