Bring Direct Mail
to VS Code Copilot
Learn how to connect Stannp to VS Code Copilot and start using 11 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Stannp MCP Server?
Connect your Stannp account to any AI agent and simplify your direct mail marketing, physical letter delivery, and mailing list management through natural conversation.
What you can do
- Physical Mail Delivery — Create and send single or bulk letters and postcards programmatically directly from your agent
- Campaign Management — Query all configured direct mail campaigns and retrieve detailed metadata and status
- Recipient Control — Query your database of contacts and mailing addresses to choose the right recipients for each piece
- Account tracking — Access your real-time account balance to manage your mailing spend
- Live Monitoring — Access a history of sent and drafted letters to stay on top of your physical outreach
How it works
1. Subscribe to this server
2. Enter your Stannp API Key from your account settings
3. Start managing your direct mail from Claude, Cursor, or any MCP-compatible client
Built-in capabilities (11)
Send a physical letter
Create and send a postcard
Create a new mailing recipient
Check account credit balance
Get details for a direct mail campaign
Get details for a specific letter
Get details for a specific recipient
List direct mail campaigns
List sent and drafted letters
List mailing recipients
List sent and drafted postcards
Why VS Code Copilot?
GitHub Copilot Agent mode brings Stannp 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.
- —
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
Stannp in VS Code Copilot
Stannp and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Stannp to VS Code Copilot through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Stannp in VS Code Copilot
The Stannp 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. All 11 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* 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
How Vinkius secures
Stannp for VS Code Copilot
Every tool call from VS Code Copilot to the Stannp MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I send a physical letter using my AI agent?
Yes! Use the create_physical_letter action. Provide the recipient details and a template ID to trigger printing and mailing programmatically.
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.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.