Can my agent list all candidates for a specific job in Greenhouse?

Yes. Use the 'list_candidates' tool with the 'job_id' parameter. The agent will fetch all candidates associated with that specific opening flawlessly.

How do I check the current hiring stage of an applicant via chat?

You can use the 'get_application' tool. Provide the Application ID, and the agent will return the full details, including the candidate's current stage in the hiring process natively.

Can I search for candidates who were added recently through the agent?

Absolutely. Use the 'list_candidates' tool with sorting or filtering parameters like 'created_after'. Your agent will retrieve the most recent additions to your Greenhouse database natively.

Greenhouse MCP Server for VS Code Copilot 12 tools — connect in under 2 minutes

Name: Greenhouse
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 12 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Greenhouse and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "greenhouse": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Greenhouse MCP Server

Connect your Greenhouse Recruiting account to any AI agent and take control of your talent acquisition pipeline through natural conversation.

GitHub Copilot Agent mode brings Greenhouse data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 12 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

Candidate Oversight — List all candidates in your system and retrieve specific profile details natively
Pipeline Tracking — Monitor job applications and their current statuses across your active hiring processes flawlessly
Job Management — List and inspect job configurations, including hiring stages and department mappings synchronously
Team Coordination — Retrieve office and department structures to ensure your hiring data is aligned with organizational goals
User Auditing — List and verify user roles and access levels within your Greenhouse workspace natively

The Greenhouse MCP Server exposes 12 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Greenhouse to VS Code Copilot via MCP

Follow these steps to integrate the Greenhouse MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Greenhouse

Ask Copilot: "Using Greenhouse, help me...". 12 tools available

Why Use VS Code Copilot with the Greenhouse MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Greenhouse through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Greenhouse + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Greenhouse MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Greenhouse MCP Tools for VS Code Copilot (12)

These 12 tools become available when you connect Greenhouse to VS Code Copilot via MCP:

create_candidate

Create a new candidate profile

get_application

Get details for a specific application

get_candidate

Get details for a specific candidate

get_job

Get details for a specific job

get_user

Get details for a specific user

list_applications

Retrieve job applications

list_candidates

List all candidates in Greenhouse

list_departments

List company departments

list_job_stages

List hiring stages for a specific job

list_jobs

List jobs in Greenhouse

list_offices

List company offices

list_users

List Greenhouse users

Example Prompts for Greenhouse in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Greenhouse immediately.

"List my active jobs in Greenhouse"

"Show me the profile for candidate ID 93021"

"What are the hiring stages for the 'Product Designer' job?"

Troubleshooting Greenhouse MCP Server with VS Code Copilot

Common issues when connecting Greenhouse to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Greenhouse + VS Code Copilot FAQ

Common questions about integrating Greenhouse MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.