How to Use the Lemlist MCP in VS Code Copilot

Q: How do I share the Lemlist MCP Server configuration in VS Code Copilot?

Create a .vscode/mcp.json file in your repository root. Commit it to Git so every developer on your team gets instant access to the MCP tools like listcampaigns.

Q: Can VS Code Copilot help me debug Lemlist API errors?

Yes. If a tool like addlead fails, VS Code Copilot inspects the raw error response and suggests the exact parameter fix inside your chat.

Q: Does VS Code Copilot support listing all active leads in a Lemlist campaign?

Yes. The listleads tool fetches the current membership of any campaign, allowing Copilot to help you analyze lead statuses or search for specific prospects.

Q: Can I query my Lemlist team configuration inside VS Code Copilot?

Yes. The getteam tool retrieves your team information directly, helping you verify permissions and seat assignments while writing team-specific routing code.

Give your team the power to manage Lemlist campaigns and sync leads directly from the VS Code Copilot chat window.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Lemlist MCP to VS Code Copilot

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Team-wide Lemlist campaign inspection

The `list_campaigns` tool lets VS Code Copilot display your active outbound tracks directly in the shared workspace. Your entire engineering team can view active campaign IDs without needing individual Lemlist accounts. When debugging webhook endpoints, `get_campaign` pulls the exact payload structure into your editor. VS Code Copilot uses this data to write flawless schema validators.

Direct lead management from VS Code Copilot

Use `add_lead` to quickly test user registration flows by pushing test accounts directly into Lemlist. You do not need to write throwaway curl scripts to verify your outreach triggers. The `delete_lead` tool lets you purge those test contacts from the campaign immediately after. This keeps your production analytics clean and prevents accidental emails to fake domains.

Granular lead state control

The `pause_lead` tool allows your team to build and test automated pause triggers inside VS Code Copilot. You can verify that your backend pause logic aligns perfectly with Lemlist's API expectations. Use `resume_lead` to test the opposite flow. This MCP Server ensures your developers can simulate the entire lead lifecycle without leaving their primary coding environment.

Setup guide

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

.vscode/mcp.json

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

Create a `.vscode/mcp.json` file in your repository root. Commit it to Git so every developer on your team gets instant access to the MCP tools like `list_campaigns`.

Yes. If a tool like `add_lead` fails, VS Code Copilot inspects the raw error response and suggests the exact parameter fix inside your chat.

Yes. The `list_leads` tool fetches the current membership of any campaign, allowing Copilot to help you analyze lead statuses or search for specific prospects.

Yes. The `get_team` tool retrieves your team information directly, helping you verify permissions and seat assignments while writing team-specific routing code.

This MCP Server keeps your lead lists, campaign details, and API tokens completely private. They are processed locally or within Vinkius's secure, zero-trust sandbox, never stored or used to train models.

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