Skip to content
Start with 100 free verification credits
Qualisend
VS Code (GitHub Copilot agent mode)
by Microsoft

Verify email in VS Code

VS Code has first-class MCP support in Copilot agent mode. Add the Qualisend endpoint and the agent can verify addresses, clean lists and check a sending domain from the chat panel.

Start free Full MCP documentation
MCP endpoint
https://app.qualisend.com/api/mcp
Authentication
Sign-in or API key
Available on
VS Code 1.102 or later, on every Copilot plan including Copilot Free. Business and enterprise orgs can disable MCP centrally.
All clients

Connect it to VS Code

You need a Qualisend account - the free plan includes 100 verification credits that never expire - and VS Code itself. Steps checked against Microsoft's documentation in September 2026.

  1. 1

    Run MCP: Add Server

    Open the Command Palette (Cmd/Ctrl+Shift+P) and run MCP: Add Server.

  2. 2

    Choose HTTP and paste the endpoint

    Pick HTTP (HTTP or Server-Sent Events), paste the endpoint, and give it the ID qualisend. Choose Workspace to write .vscode/mcp.json, or Global for all your projects.

    https://app.qualisend.com/api/mcp
  3. 3

    Add your key, or skip for sign-in

    For a static key, edit the generated file to match the block below - VS Code prompts once and stores the value in the secret store. For sign-in, leave the file as just type and url.

  4. 4

    Start it and pick the tools

    Click Start above the server entry. Then open Chat, select Agent from the agent picker, select Configure Tools in the chat input and confirm the Qualisend tools are ticked.

Sign-in or API key

Either. With no headers, VS Code runs the browser sign-in on first connect. With the input-prompted header below, it asks once for your API key and keeps it in the OS secret store.

Check that it worked

Ask "how many Qualisend credits do I have left?". A number back means you are connected - that tool is free, so it costs nothing to test.

Config file

.vscode/mcp.json

The root key is servers. Not mcpServers - that is the portable format used by other tools, and VS Code ignores it here without a word.

{
  "inputs": [
    {
      "type": "promptString",
      "id": "qualisend-key",
      "description": "Qualisend API key",
      "password": true
    }
  ],
  "servers": {
    "qualisend": {
      "type": "http",
      "url": "https://app.qualisend.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${input:qualisend-key}"
      }
    }
  }
}

Worth knowing

  • The root key in .vscode/mcp.json is servers, not mcpServers. VS Code silently ignores an mcpServers object here - this is the most common failure by far.
  • Use ${input:...} rather than ${env:...} inside headers. Environment substitution there has been buggy, and the input form keeps the key in the secret store instead of a file.
  • Three config shapes coexist: .vscode/mcp.json (servers), the portable .mcp.json at the repo root (mcpServers), and the user-level Copilot config. Check which file you actually opened.
  • A workspace .vscode/mcp.json is trust-gated - VS Code asks before starting servers from a folder you have not trusted.

What to ask once it is connected

There are no commands to learn. Ask in your own words and VS Code picks the right tool - there are twelve, covering verification, sending-domain deliverability and blacklist checks.

“Verify every address in the seed data and list the undeliverable ones.”
“Before I ship this form, check whether this domain accepts mail at all.”
“Clean the sample list in test/fixtures and summarise what changed.”
“How many verification credits do I have left?”

What VS Code can reach

Only the verification tools, scoped to the single workspace you connect. It cannot reach another customer's data, your billing, or any admin function, and it never sees how a check is performed - just the verdict and the score. Authentication is an explicit token in a request header, never a cookie, so there is no session for a malicious page to borrow. Revoke it from VS Code or from your Qualisend dashboard at any time; sign-in access also expires on its own within an hour. Full detail is on the MCP documentation page.

VS Code FAQ

Microsoft's own reference: VS Code MCP docs

Using something else?

It is the same endpoint everywhere. Pick your client:

ClaudeChatGPTGrokClaude CodeCursorCodex CLIGemini CLIZedGooseWindsurf

Any other MCP-compatible client works too - Cline, JetBrains AI Assistant and the rest all take the same Streamable HTTP endpoint. The MCP documentation has the transport and authentication details.

Ready to connect VS Code?

Start free with 100 credits that never expire, then paste the endpoint.

Start free MCP overview