What is the key difference between Greenhouse and Calendly?

Greenhouse belongs to the Developer Tools category with cloud HTTP/SSE execution, while Calendly belongs to the Developer Tools category with cloud HTTP/SSE execution.

How do I install Greenhouse or Calendly in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Greenhouse and Calendly free or paid?

Greenhouse operates under a Free / Open Source model (No auth required). Calendly operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Greenhouse lists 5 tools with 0 views and 0 GitHub stars. Calendly lists 5 tools with 0 views and 0 GitHub stars.

Can I use both Greenhouse and Calendly together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Greenhouse vs Calendly

In-depth architectural comparison of the Greenhouse and Calendly 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

Greenhouse

Developer Tools · Remote HTTP/SSE

Quality: 49/100 (Fair) | Auth: No auth required

Calendly

Developer Tools · Remote HTTP/SSE

Quality: 51/100 (Good) | Auth: No auth required

Verdict Summary: Choose Greenhouse if you need specialized Developer Tools tools running via a hosted cloud SSE transport. Choose Calendly 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?

Choose Greenhouse 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).
Primary tools included: greenhouse_list_candidates, greenhouse_get_candidate, greenhouse_list_jobs.

Explore Greenhouse Details

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).
Primary tools included: current_user, list_scheduled_events, get_event.

Explore Calendly Details

Feature & Specification Comparison

Specification	G Greenhouse Developer Tools	C Calendly Developer Tools
Summary	Greenhouse MCP Pack — wraps the Greenhouse Harvest API v1	Calendly MCP Pack — wraps the Calendly API v2 for scheduling data.
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

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').

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).

Greenhouse Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "greenhouse": {
      "url": "https://pipeworx.io"
    }
  }
}

Calendly Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "calendly": {
      "url": "https://pipeworx.io"
    }
  }
}

Frequently Asked Questions

Greenhouse is categorized under Developer Tools and uses a remote streaming HTTP/SSE transport. In contrast, Calendly belongs to Developer Tools using remote streaming HTTP/SSE transport. Select Greenhouse when you need capabilities focused on developer tools and Calendly when you require tools for developer tools.

More alternatives to Greenhouse More alternatives to Calendly Developer Tools category hub Canonical compare URL