Calendly vs Greenhouse — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Calendly vs Greenhouse
In-depth architectural comparison of the Calendly and Greenhouse MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Calendly
Developer Tools · Remote HTTP/SSE
Quality: 51/100 (Good) | Auth: No auth required
Greenhouse
Developer Tools · Remote HTTP/SSE
Quality: 49/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Calendly if you need specialized Developer Tools tools running via a hosted cloud SSE transport. Choose Greenhouse if your workspace requires Developer Tools integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
C
Choose Calendly when:
You need dedicated capabilities in the Developer Tools domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Get the current Calendly user for the supplied token. Returns the user URI and organization URI — call this FIRST, since list_scheduled_events and list_event_types require a user or organization URI.
list_scheduled_events
List scheduled meetings (events). Requires a user URI OR an organization URI (get them from current_user). Filter by status, time window, and paginate. Returns event URIs/UUIDs, names, start/end times, status, and locations.
get_event
Get a single scheduled event by its UUID (the last path segment of an event URI). Returns full event details including name, times, status, location, and event membership.
list_invitees
List the invitees of a scheduled event by event UUID. Returns invitee names, emails, status (active/canceled), timezone, and answers to booking questions.
list_event_types
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Calendly is categorized under Developer Tools and uses a remote streaming HTTP/SSE transport. In contrast, Greenhouse belongs to Developer Tools using remote streaming HTTP/SSE transport. Select Calendly when you need capabilities focused on developer tools and Greenhouse when you require tools for developer tools.
List bookable event types (meeting templates). Requires a user URI OR an organization URI (get them from current_user). Returns event type URIs, names, durations, scheduling URLs, and active state.
Greenhouse Tools (5)
greenhouse_list_candidates
Search candidates in your ATS. Returns names, IDs, email addresses, and application status. Use greenhouse_get_candidate for full profile details.
greenhouse_get_candidate
Get full candidate profile by ID. Returns resume, contact info, application history, interviews, and notes.
greenhouse_list_jobs
Browse open and closed job postings. Returns titles, IDs, departments, statuses, and posting dates. Use greenhouse_get_job for full details and candidate pipeline.
greenhouse_get_job
Get complete job details by ID. Returns description, requirements, hiring team, and linked applications.
greenhouse_list_applications
View job applications across your pipeline. Returns applicant names, job IDs, application status, and submission dates. Filter by job or stage (e.g., 'screening', 'interview').