How to Use the Five9 MCP in VS Code Copilot

Q: How do we roll out the Five9 MCP Server to a team using VS Code Copilot?

Add the Five9 server configuration to your team's .vscode/mcp.json file and commit it to Git so VS Code Copilot detects it automatically.

Q: Can VS Code Copilot help us debug Five9 campaign configurations?

Yes, the VS Code Copilot agent calls listcampaigns to retrieve your active Five9 dialer setups.

Q: How does this integration secure our Five9 contact center metadata in VS Code Copilot?

All metadata retrieved by listagentstates or listusers is processed in an ephemeral V8 sandbox, meaning Vinkius never caches your Five9 contact center details during your VS Code Copilot sessions.

Equip your entire engineering team with live Five9 management tools in 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 Five9 MCP to VS Code Copilot

Create your Vinkius account to connect Five9 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 Five9 with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Share the Five9 MCP Server across your dev team

Standardize your development workflow by checking `.vscode/mcp.json` into your shared repository so every developer on your team immediately gains access to Five9 tools like `list_users` and `list_agent_groups` inside VS Code Copilot. This shared MCP Server setup ensures that everyone debugs Five9 routing logic using the same environment. Team members can inspect active Five9 configurations inside VS Code Copilot without sharing administrative passwords directly.

Troubleshoot call routing issues during development

When debugging custom routing scripts, VS Code Copilot uses `list_skills` to verify your code targets active Five9 queues. You do not have to guess if a Five9 queue exists because VS Code Copilot checks the live server configuration for you. If a test call hangs up your environment, instruct VS Code Copilot to run `list_active_interactions` to locate the stuck Five9 session. Running `terminate_interaction` directly from the VS Code Copilot chat panel clears the Five9 queue.

Monitor test agent states without leaving your editor

Keep track of your sandbox Five9 agents while writing backend integrations in VS Code Copilot. VS Code Copilot monitors Five9 agent availability by querying `get_agent_state` and displays current statuses directly in your workspace. When you need to reset your testing environment, tell the VS Code Copilot agent to run `update_agent_state` or `logout_session` to reset Five9 states. This keeps your focus on the code instead of administrative Five9 overhead in VS Code Copilot.

Setup guide

Set up Five9 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 Five9 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 Five9 tools listed. Try asking: "List my recent Five9 transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

{
  "mcpServers": {
    "five9-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 Five9. 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 Five9 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 Five9 MCP in VS Code Copilot

Add the Five9 server configuration to your team's `.vscode/mcp.json` file and commit it to Git so VS Code Copilot detects it automatically.

Yes, the VS Code Copilot agent calls `list_campaigns` to retrieve your active Five9 dialer setups.

The integration routes requests through Vinkius, which manages API pacing to prevent your Five9 keys from getting throttled while testing inside VS Code Copilot.

Yes, access is controlled via your Vinkius MCP token permissions, allowing you to issue read-only tokens that let developers query `get_agent_state` but block destructive Five9 tools inside VS Code Copilot.

All metadata retrieved by `list_agent_states` or `list_users` is processed in an ephemeral V8 sandbox, meaning Vinkius never caches your Five9 contact center details during your VS Code Copilot sessions.

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