How to Use the Greenhouse MCP in VS Code Copilot

Q: How do I set up Greenhouse tools in VS Code Copilot?

Create a .vscode/mcp.json file in your repository root. Add the Greenhouse MCP Server details, and anyone opening the project in VS Code 1.96+ can use the tools in Copilot Chat.

Deploy team-wide Greenhouse recruiting tools inside VS Code Copilot to inspect pipelines and write custom HR integrations.

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

Share Greenhouse MCP Server configs across your team

Standardize your Greenhouse recruitment development environment by committing your configuration directly to your repository. VS Code Copilot reads `.vscode/mcp.json` to give every engineer immediate access to the Greenhouse MCP tools. New developers on the team do not need to configure Greenhouse manually inside VS Code. They open the VS Code workspace, and Copilot is instantly ready to query Greenhouse `list_jobs` or inspect hiring stages using `list_job_stages`.

Verify user permissions and roles in VS Code Copilot

Auditing Greenhouse access control is simple when your VS Code Copilot editor can query your user directory directly. Use VS Code Copilot to run `list_users` and `get_user` to check who has access to sensitive Greenhouse recruiting pipelines. Your team can quickly identify stale Greenhouse accounts or incorrect role assignments in VS Code Copilot. Copilot displays the Greenhouse results in your VS Code sidebar, making security audits a matter of a simple chat query.

Build custom application trackers with live data

Stop guessing how Greenhouse candidate applications are structured when coding in VS Code. VS Code Copilot pulls live Greenhouse records using `list_applications` and `get_application` to help you map out custom tracking dashboards. The VS Code Copilot editor uses these live Greenhouse payloads to write clean, typed components. It ensures your custom Greenhouse dashboards handle actual applicant data structures without throwing runtime errors.

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-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 repository root. Add the Greenhouse MCP Server details, and anyone opening the project in VS Code 1.96+ can use the tools in Copilot Chat.

Yes, it can. Ask Copilot to register a candidate, and it will execute the `create_candidate` tool to add the profile directly to your ATS.

Yes, you can configure it globally. Use the command palette to open your user configuration, allowing you to access the recruiting MCP tools across all your workspaces.

No, you can manage access centrally. The server uses your organization's configured token, so developers only need access to the VS Code workspace to run queries.

All communication between VS Code Copilot and the ATS is encrypted end-to-end. Your job application data and user profiles are processed locally, ensuring no sensitive recruitment details are cached externally.

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