How to Use the Greenhouse MCP in VS Code Copilot

Q: How do I share the Greenhouse setup with my team in VS Code Copilot?

Create a .vscode/mcp.json file in your project root and commit it to your Git repository. Once your team pulls the changes, they can use the MCP server configuration in Copilot Chat.

Q: Can we check candidate details from Greenhouse using VS Code Copilot?

Yes, the getcandidatedetails tool pulls full profiles into your chat. This lets you review resumes and application histories during code reviews.

Q: How do we verify our Greenhouse credentials in VS Code Copilot?

Use the getapistatus tool to check your active connection. It verifies that your team's configuration is authenticating properly.

Q: Can we see which positions are currently open?

Yes, listopenjobs retrieves all active openings. You can use this to see which teams have open headcount before referring a candidate.

Share a common Greenhouse hiring configuration across your entire engineering team inside VS Code Copilot.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Greenhouse MCP to VS Code Copilot

Create your Vinkius account to connect Greenhouse to VS Code Copilot and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Greenhouse with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Team-Wide Pipeline Management with this MCP Server

`list_candidates` lets your whole team access the applicant pool from a shared workspace configuration via this MCP Server. Developers can review incoming technical profiles without needing separate recruiter accounts. By committing the server setup to your repository, every engineer gets access to `get_candidate_details` instantly. This makes technical screening reviews collaborative and fast.

Standardize Candidate Referrals

`create_candidate` allows engineers to refer talent directly from their development environment. They just pass the first name, last name, and company to the tool to log the referral. Once the candidate is in the system, you can use `update_candidate` to add notes from code reviews or technical challenges. This keeps all feedback in one central place.

Automate Screenings and Rejections

`reject_application` handles candidate rejections directly from your editor when a technical test fails. You must provide a valid rejection reason ID to log the decision correctly in your tracking system. If the candidate passes, `advance_application` moves them to the next interview stage. This keeps the hiring process moving without forcing engineers to log into a separate web portal.

Setup guide

Set up Greenhouse MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the Greenhouse MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the Greenhouse tools listed. Try asking: "List my recent Greenhouse transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

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

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Greenhouse. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Greenhouse now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Greenhouse MCP in VS Code Copilot

Create a `.vscode/mcp.json` file in your project root and commit it to your Git repository. Once your team pulls the changes, they can use the MCP server configuration in Copilot Chat.

Yes, the `get_candidate_details` tool pulls full profiles into your chat. This lets you review resumes and application histories during code reviews.

Use the `get_api_status` tool to check your active connection. It verifies that your team's configuration is authenticating properly.

Yes, `list_open_jobs` retrieves all active openings. You can use this to see which teams have open headcount before referring a candidate.

Your applicant profiles and company structure are kept safe through tokenized authentication. The MCP Server runs inside an ephemeral sandbox, meaning no candidate data is cached or stored after the tool finishes running.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript