How do I get a Dixa API Token?

Log in to your Dixa account as an administrator, navigate to **Settings > Integrations > API Tokens**, and click **Create Token**. Note that you may need a specific plan for API access.

Can the agent reply to customers?

This integration currently focuses on listing and auditing conversations, agents, and queues. Sending replies to customers should be managed via the Dixa agent interface.

Does the integration show real-time agent presence?

Yes, you can use the list_service_agents or quick_agent_presence_audit tools to see the current presence status of your support team.

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

Name: Dixa
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 Dixa and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "dixa": {
      "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 Dixa MCP Server

Integrate Dixa, the customer friendship platform, directly into your AI workflow. Manage your multi-channel support conversations, monitor agent presence and performance, track service queues, and oversee your support teams using natural language.

GitHub Copilot Agent mode brings Dixa 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.

What you can do

Conversation Oversight — List and retrieve detailed information for all customer conversations and their current processing status.
Agent Intelligence — Monitor real-time agent presence, profile details, and team assignments across your organization.
Queue Monitoring — Track active service queues and routing settings to ensure efficient support delivery.
Team Management — List all support teams and identify members assigned to specific organizational units.

The Dixa 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 Dixa to VS Code Copilot via MCP

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

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

Why Use VS Code Copilot with the Dixa MCP Server

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

Dixa + VS Code Copilot Use Cases

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

Dixa MCP Tools for VS Code Copilot (10)

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

get_agent_profile

Get full profile and performance data for a specific agent

get_conversation_details

Get detailed information for a specific customer conversation

get_service_account_metadata

Retrieve metadata and usage limits for your Dixa account

list_customer_conversations

List all customer service conversations in your Dixa account

list_open_support_tickets

Identify conversations that are currently in an "Open" or "Unassigned" status

list_service_agents

List all support agents registered in your Dixa organization

list_service_queues

List all active service queues configured in Dixa

list_support_teams

List all configured support teams and their members

quick_agent_presence_audit

Retrieve a high-level summary of active agent presence statuses

search_conversations_by_subject

Search for conversations using a keyword in the subject

Example Prompts for Dixa in VS Code Copilot

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

"List all open support conversations."

"Show me the details for conversation '12345'."

"Who is currently available in the 'Sales' team?"

Troubleshooting Dixa MCP Server with VS Code Copilot

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

Dixa + VS Code Copilot FAQ

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