How do I get my Appcues API Key and Secret?

You can generate API keys in the Appcues Studio. Go to **Settings > Integrations > API Keys** to create a new set of credentials.

What is my Appcues Account ID?

Your Account ID is a unique numeric identifier for your Appcues account. You can find it in the URL of your Appcues Studio (e.g., studio.appcues.com/accounts/YOUR_ID) or in your Account Settings.

Does this server support the EU region?

Yes, you can configure the `APPCUES_REGION` environment variable to `eu` if your account is hosted in the Appcues European data center.

Appcues MCP Server for VS Code Copilot 11 tools — connect in under 2 minutes

Name: Appcues
Availability: InStock
Author: Vinkius

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

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

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "appcues": {
      "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 Appcues MCP Server

The Appcues MCP Server empowers your AI agent to interact directly with your Appcues account. Whether you need to audit your current onboarding flows, manage user segments, or track real-time user activity, this integration provides a seamless natural language interface to your product experience platform.

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

Key Features

Flow Management — List, view, publish, and unpublish flows (in-app experiences) across web and mobile.
User Segmentation — Retrieve and analyze your targeting segments to understand who is seeing your content.
Activity Tracking — Send real-time events and profile updates for immediate targeting and personalization.
Mobile Support — Access specific experiences designed for your mobile applications.
Auditing & Reporting — Quickly check account status, checklists, and experience metadata.

Benefits for Teams

Product Managers — Quickly audit which onboarding flows are active and make changes without leaving your AI workspace.
Growth Engineers — Programmatically track user events to trigger personalized in-app journeys.
Customer Success — View user profiles and segment membership to provide better support and guidance.

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

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

Ask Copilot: "Using Appcues, help me...". 11 tools available

Why Use VS Code Copilot with the Appcues MCP Server

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

Appcues + VS Code Copilot Use Cases

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

Appcues MCP Tools for VS Code Copilot (11)

These 11 tools become available when you connect Appcues to VS Code Copilot via MCP:

get_account_details

Verify Appcues account connection

get_flow

Get details for a specific flow

get_segment

Get details for a specific segment

get_user_profile

Retrieve the profile of a specific user

list_checklists

List all checklists configured in the account

list_flows

List all Appcues flows (experiences) for the account

list_mobile_experiences

List mobile-specific experiences

list_segments

List all user segments defined in Appcues

publish_flow

Publish a draft flow

track_user_activity

Use JSON strings for profileUpdate and events. Track real-time events and profile updates for a user

unpublish_flow

Unpublish an active flow

Example Prompts for Appcues in VS Code Copilot

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

"List all my active Appcues flows."

"Track a 'clicked_checkout' event for user 'user_123'."

"Show me the details of the segment with ID '998877'."

Troubleshooting Appcues MCP Server with VS Code Copilot

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

Appcues + VS Code Copilot FAQ

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