# Callendar [Health: Active]

**Category:** 💬 Communication  
**Repository:** https://callendar.co/  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/callendar

## Description
WhatsApp® reminders and rescheduling for Calendly. Public read-only MCP endpoint.

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "callendar": {
    "command": "npx",
    "args": ["-y","callendar"]
  }
}
```

## Documentation

## What the Callendar MCP server does

The Callendar MCP server is presented as a bridge between WhatsApp reminders and Calendly scheduling workflows. Its stated purpose covers sending or managing reminders through WhatsApp and handling rescheduling for Calendly. The available project description does not identify additional calendar providers, messaging platforms, or scheduling systems.

The service is also described as a public MCP endpoint. That makes it relevant for MCP clients or agents that need to connect to a hosted service rather than deploy a server locally. However, the listing characterizes the endpoint as read-only, so the available information does not establish that an agent can create, update, or cancel Calendly events through MCP.

## How it works

The Callendar MCP server is accessed over its public MCP endpoint. An MCP-compatible client can use the endpoint as the connection point for the capabilities exposed by Callendar, subject to the endpoint's read-only behavior. The supplied material does not specify the transport, endpoint path, authentication method, request format, or individual MCP tool names.

Its documented workflow combines two systems: WhatsApp for reminders and Calendly for scheduling and rescheduling. The source description does not explain whether reminders are triggered by Calendly events, configured manually, or generated through another workflow. Those implementation details should be confirmed before integrating it into an automated process.

## Setup and configuration

No installation steps, configuration file, package, command, or environment variable are provided in the available material. Because the Callendar MCP server is described as public, local deployment may not be required, but the exact connection instructions are not documented here. Consult the service's current documentation at callendar.co for the endpoint details and any client-specific setup guidance.

The available information also does not state whether authentication is required despite the endpoint being public. Do not assume that a public endpoint is anonymous or that it is suitable for sending sensitive calendar information without checking its access and data-handling requirements.

## Limitations and notes

The main constraint is the read-only designation. Although the product description mentions Calendly rescheduling, the supplied material does not clarify how that function relates to a read-only MCP endpoint. The Callendar MCP server should therefore be evaluated against the exact operations exposed by the live service rather than assumed to support calendar mutations.

No README is available for this listing, and no tool inventory, supported client list, authentication guidance, rate limits, data-retention policy, or license information is provided. There is also no evidence here of compatibility with a particular desktop assistant or coding editor. Treat those areas as undetermined until the provider documents them.

_Full upstream README: https://allmcps.com/mcp/callendar/readme_