Side-by-Side Model Context Protocol Comparison
Close Crm vs Greenhouse
In-depth architectural comparison of the Close Crm 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
Close Crm
Developer Tools · Local stdio
Quality: 44/100 (Fair) | Auth: No auth required
Greenhouse
Developer Tools · Local stdio
Quality: 44/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Close Crm if you need specialized Developer Tools tools running via a local process. Choose Greenhouse if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's
mcpServers manifest.Which MCP Server Should You Choose?
C
Choose Close Crm when:
- You need dedicated capabilities in the Developer Tools domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
- Primary tools included: close_me, close_search_leads, close_get_lead.
G
Choose Greenhouse when:
- You need dedicated capabilities in the Developer Tools domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
- Primary tools included: greenhouse_list_candidates, greenhouse_get_candidate, greenhouse_list_jobs.
Feature & Specification Comparison
Tools & Capabilities Breakdown
Close Crm Tools (6)
close_me
Get the current Close user and organization for the supplied API key. Returns user ID, name, email, and the organizations (with IDs) the key can access. Use this to verify the key works and discover your organization context.
close_search_leads
Search or list leads (companies/accounts in Close) using Close's query language. Returns a `data` array of leads (with id, display_name, contacts, status, custom fields) plus `has_more` and `total_results`. The `query` param accepts Close search syntax, e.g. `name:"Acme"`, `status_label:"Potential"…
close_get_lead
Get a single lead by its Close lead ID (format `lead_...`). Returns full detail: display name, description, status, contacts, addresses, opportunities, custom fields, and timestamps.
close_list_opportunities
List opportunities (pipeline deals) in Close. Returns a `data` array of opportunities with id, lead_id, status, value, currency, confidence, and expected close date, plus `has_more` / `total_results`. Pass `lead_id` to scope to one lead, or omit to list across the organization. Page with `_limit` /…
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).
Close Crm Configuration
Greenhouse Configuration