mcp-calendly
# @nimblebraininc/calendly
MCP server for the [Calendly API](https://developer.calendly.com/api-docs). Browse event types, view and filter scheduled meetings, inspect invitee details, check availability windows, and cancel events.
## Tools
| Tool | Description |
|------|-------------|
| `get_current_user` | Get the authenticated user's profile |
| `list_event_types` | List the user's event types |
| `list_scheduled_events` | List scheduled events with optional filters |
| `get_event` | Get details of a specific scheduled event |
| `list_invitees` | List invitees for a scheduled event |
| `cancel_event` | Cancel a scheduled event with an optional reason |
| `check_availability` | Get available time slots for an event type |
## Setup
1. Get a Personal Access Token from [Calendly Integrations](https://calendly.com/integrations/api_webhooks)
2. Configure via mpak:
```bash
mpak config set @nimblebraininc/calendly api_key your_token_here
```
## Development
```bash
npm install
npm run build
npm run check # format, lint, typecheck, tests
```
## License
MIT
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose targeting specific resources and actions in the Calendly domain. For example, 'get_event' retrieves details of a single event, while 'list_scheduled_events' lists multiple events with filters, and 'cancel_event' performs a distinct cancellation action. There is no overlap or ambiguity in functionality.
All tool names follow a consistent verb_noun pattern with clear, descriptive actions (e.g., 'cancel_event', 'get_current_user', 'list_event_types'). The naming is uniform across all seven tools, using snake_case consistently without any deviations or mixed conventions.
With 7 tools, this server is well-scoped for managing Calendly events and user interactions. The count is appropriate for the domain, covering core operations like checking availability, listing events, and managing event details without being overly sparse or bloated.
The tool set provides strong coverage for core Calendly workflows, including event listing, retrieval, cancellation, availability checks, and user profile access. A minor gap exists in the lack of a tool for creating or scheduling new events, which agents might need to work around, but the surface is otherwise comprehensive for the inferred domain.