How do I find my ApplicantStack API Token?

Log in to ApplicantStack, go to **Settings**, then **Edit Settings**. Your API token will be listed under the API section.

What is the subdomain?

The subdomain is the first part of your ApplicantStack URL (e.g., if your URL is `mycompany.applicantstack.com`, your subdomain is `mycompany`).

Can I move a candidate to a new stage?

Yes, use the `update_candidate` tool and provide the new stage name in the `stage` field to advance them in your workflow.

ApplicantStack MCP Server for VS Code Copilot 7 tools — connect in under 2 minutes

Name: ApplicantStack
Availability: InStock
Author: Vinkius

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

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

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "applicantstack": {
      "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 ApplicantStack MCP Server

The ApplicantStack MCP Server integrates your recruiting and onboarding workflows directly into your AI workspace. Efficiently manage your job listings, track candidate progress through custom stages, and streamline your hiring process using simple natural language.

GitHub Copilot Agent mode brings ApplicantStack data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 7 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 active and closed job openings, and retrieve full metadata for any specific listing.
Candidate Tracking — Access your entire applicant database and filter by workflow stage or score.
Workflow Automation — Move candidates between stages (e.g., from 'Interview' to 'Hired') and update their profiles instantly.
Onboarding & Hires — Access onboarding data for new hires to ensure a smooth transition from applicant to employee.
Secure Access — Uses private access tokens to safely interact with your organization's recruiting data.

Benefits for Teams

Recruiters — Quickly check the status of candidates for multiple jobs without switching between tabs.
Hiring Managers — Review candidate profiles and scores using AI-assisted summaries.
HR Teams — Track hiring trends and ensure onboarding tasks are initiated for all new hires.

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

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

Ask Copilot: "Using ApplicantStack, help me...". 7 tools available

Why Use VS Code Copilot with the ApplicantStack MCP Server

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

ApplicantStack + VS Code Copilot Use Cases

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

ApplicantStack MCP Tools for VS Code Copilot (7)

These 7 tools become available when you connect ApplicantStack to VS Code Copilot via MCP:

get_account_check

Verify ApplicantStack account connection

get_candidate

Get details for a specific candidate

get_job

Get details for a specific job

list_candidates

List all candidates

list_hires

List all hires (onboarding)

list_jobs

List all job listings in ApplicantStack

update_candidate

Use stage field to move them in the workflow. Update candidate information or stage

Example Prompts for ApplicantStack in VS Code Copilot

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

"List all active job openings in ApplicantStack."

"Show me candidates currently in the 'Interview' stage."

"Move candidate 'C12345' to the 'Hired' stage."

Troubleshooting ApplicantStack MCP Server with VS Code Copilot

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

ApplicantStack + VS Code Copilot FAQ

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