How do I find my Ashby API Key?

Log in to Ashby, go to **Admin > API Keys**, and click **Create API Key**. Ensure you grant the necessary permissions (e.g., `jobsRead`, `candidatesRead`).

Why does this server use POST for all requests?

The Ashby API is designed as an RPC-style API where even data retrieval (reading) endpoints require a POST request with a JSON body.

Can I search for candidates by email?

Yes, use the `search_candidates` tool and provide the `email` parameter to find a specific candidate in your database.

Ashby MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Name: Ashby
Availability: InStock
Author: Vinkius

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

Built by Vinkius GDPR 10 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 Ashby and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "ashby": {
      "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 Ashby MCP Server

The Ashby MCP Server provides a direct natural language interface to your Ashby recruiting platform. Empower your AI agent to manage your hiring pipeline, from job listing analysis to candidate search and application tracking.

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

Key Features

Job Management — List all open, closed, and archived jobs, and retrieve detailed metadata for any specific position.
Candidate Sourcing — Search for candidates by name or email and access full profiles, including tags and contact details.
Application Tracking — Monitor the status of job applications and filter by job ID or workflow stage (e.g., Hired, Lead).
Interview Oversight — Retrieve lists of scheduled interviews to stay on top of your recruiting calendar.
Search Intelligence — Use powerful search tools to quickly find the right talent or job openings in your organization.
Secure Integration — Uses secure HTTP Basic Authentication with your Ashby API key.

The Ashby MCP Server exposes 10 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 Ashby to VS Code Copilot via MCP

Follow these steps to integrate the Ashby 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 Ashby

Ask Copilot: "Using Ashby, help me...". 10 tools available

Why Use VS Code Copilot with the Ashby MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Ashby 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

Ashby + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Ashby 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

Ashby MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Ashby to VS Code Copilot via MCP:

get_account_check

Verify Ashby account connection

get_application_info

Get details for a specific application

get_candidate_info

Get detailed information for a specific candidate

get_job_info

Get detailed information for a specific job

list_applications

List all job applications

list_candidates

List all candidates in Ashby

list_interviews

List all interviews

list_jobs

Supports status filtering. List all job listings in Ashby

search_candidates

Search for candidates by email or name

search_jobs

Search for jobs by title

Example Prompts for Ashby in VS Code Copilot

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

"List all currently opened jobs in Ashby."

"Search for a candidate named 'John Doe'."

"Show me the details of application 'app_998877'."

Troubleshooting Ashby MCP Server with VS Code Copilot

Common issues when connecting Ashby 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.

Ashby + VS Code Copilot FAQ

Common questions about integrating Ashby 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.