How do I find my Inbox ID?

Use the `list_all_inboxes` tool to see a comprehensive list of all your MailSlurp addresses along with their unique IDs.

What is the benefit of the 'wait-for' tools?

They hold the connection until an email arrives, making it easy to test asynchronous processes (like password resets) without writing complex retry loops.

Where do I find my API Key?

Log in to your MailSlurp dashboard and copy the API key from the Home or API Settings section.

MailSlurp MCP Server for VS Code Copilot 8 tools — connect in under 2 minutes

Name: MailSlurp
Availability: InStock
Author: Vinkius

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

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

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "mailslurp": {
      "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 MailSlurp MCP Server

Connect your MailSlurp account to any AI agent to automate your email testing and asynchronous message management. This MCP server enables your agent to create virtual inboxes, send and receive emails, and handle complex automation scenarios using long-polling 'wait-for' methods directly from natural language interfaces.

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

What you can do

Virtual Inbox Management — Create random or custom email addresses and list all managed inboxes in your account
Email Automation — Long-poll for the latest incoming email or wait until a specific email count is reached for testing suites
Message Retrieval — List and inspect messages received by any virtual address, including full HTML and text bodies
Outbound Capability — Send emails directly from any of your MailSlurp addresses programmatically
Infrastructure Maintenance — Permanently delete individual messages or entire virtual inboxes via simple commands
Metadata Inspection — Retrieve detailed technical headers and attachment metadata for any received email

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

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

Ask Copilot: "Using MailSlurp, help me...". 8 tools available

Why Use VS Code Copilot with the MailSlurp MCP Server

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

MailSlurp + VS Code Copilot Use Cases

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

MailSlurp MCP Tools for VS Code Copilot (8)

These 8 tools become available when you connect MailSlurp to VS Code Copilot via MCP:

create_random_inbox

Create a new random email address

delete_specific_inbox

Delete an inbox and its emails

get_email_details

Get complete content for a specific email

list_all_inboxes

List all MailSlurp inboxes

list_inbox_emails

List emails received by an inbox

send_email_from_inbox

Requires recipient and content. Send an email using a MailSlurp address

wait_for_email_count

Wait until an inbox has a certain number of emails

wait_for_latest_email

Returns the latest one immediately if present. Long-poll for the next incoming email

Example Prompts for MailSlurp in VS Code Copilot

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

"Create a new random inbox in MailSlurp."

"Wait for the next email to arrive in inbox 'inbox-xyz'."

"Send an email to 'user@example.com' from inbox 'inbox-xyz'."

Troubleshooting MailSlurp MCP Server with VS Code Copilot

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

MailSlurp + VS Code Copilot FAQ

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