How do I get Emarsys API credentials?

Log in to your Emarsys account, navigate to **Admin > Web Services**, and you can create or retrieve your **API Username** and **Secret Key**. Ensure the user has the required permissions for the resources you wish to access.

What authentication method does this integration use?

This integration uses **W-SSE authentication**, which is the standard for the Emarsys API. It requires both your API Username and Secret Key to securely generate request headers.

Can the agent trigger automation programs?

This integration currently focuses on listing and auditing programs and events. Triggering specific automation workflows should be managed via external events in the Emarsys dashboard or dedicated transactional API calls.

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

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

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "emarsys": {
      "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 Emarsys MCP Server

Integrate Emarsys, the comprehensive customer engagement platform, directly into your AI workflow. Manage your email marketing campaigns and contact lists, track audience segments and automation programs, monitor trigger events and registration forms, and oversee your omnichannel engagement using natural language.

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

Campaign Oversight — List and retrieve detailed information, subject lines, and launch statuses for all your email campaigns.
Contact Intelligence — Monitor marketing contact lists and audience segments, resolving structural details and filter criteria.
Automation Management — Access and monitor automation programs and workflows, tracking active statuses and trigger events.
Engagement Auditing — Retrieve high-level summaries of campaign volume, list activity, and organizational marketing health instantly.

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

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

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

Why Use VS Code Copilot with the Emarsys MCP Server

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

Emarsys + VS Code Copilot Use Cases

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

Emarsys MCP Tools for VS Code Copilot (10)

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

get_campaign_details

Get detailed settings and status for a specific email campaign

get_contact_list_details

Get detailed settings for a specific contact list

get_emarsys_account_metadata

Retrieve metadata and settings for your Emarsys account

list_audience_segments

List all audience segments (filters) in your account

list_automation_programs

List all automation programs and workflows

list_email_campaigns

List all email campaigns in your Emarsys account

list_marketing_contact_lists

List all contact lists configured in your organization

list_registration_forms

List all subscription and registration forms

list_trigger_events

List all external events used for triggering automation programs

quick_engagement_volume_audit

Retrieve a high-level summary of campaigns, lists, and automation programs

Example Prompts for Emarsys in VS Code Copilot

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

"List all active email campaigns."

"Show me the audience segments in my account."

"What automation programs are currently running?"

Troubleshooting Emarsys MCP Server with VS Code Copilot

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

Emarsys + VS Code Copilot FAQ

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