Bring Web Push
to VS Code Copilot
Learn how to connect PushEngage to VS Code Copilot and start using 7 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the PushEngage MCP Server?
Connect your PushEngage account to any AI agent and take full control of your web push notification ecosystem and high-fidelity outreach orchestration through natural conversation.
What you can do
- Notification Portfolio Orchestration — List all push notifications and broadcasts, retrieve detailed high-fidelity status metadata, and monitor campaign performance programmatically
- Subscriber Intelligence Architecture — Access complete high-fidelity subscriber profiles and activity history to understand your audience directly through your agent
- Broadcast Orchestration — Programmatically trigger new high-fidelity push broadcasts to specific segments for perfectly coordinated audience engagement
- Segment Analysis — Access your complete directory of high-fidelity subscriber segments to optimize your targeting strategy and campaign relevance
- Automation Discovery — Access high-fidelity automation workflows and trigger settings to understand and orchestrate your outreach pipelines
- Operational Monitoring — Verify account-level API connectivity and monitor notification volume directly through your agent for perfectly coordinated service scaling
How it works
1. Subscribe to this server
2. Retrieve your API Key from your PushEngage dashboard (Settings > Site Settings > API Keys)
3. Start managing your push notification growth from Claude, Cursor, or any MCP client
No more manual notification drafting or missing campaign gaps. Your AI acts as your dedicated push coordinator and outreach architect.
Who is this for?
- Growth Marketers — instantly retrieve campaign analytics and trigger time-sensitive broadcasts using natural language commands
- Customer Success Leads — analyze high-fidelity subscriber segments and monitor engagement trends to ensure healthy audience relationships
- Operations Managers — verify technical API logs and monitor automation performance through simple AI queries
Built-in capabilities (7)
Check API Status
List push notifications
List subscriber segments
List registered sites
List push subscribers
List automation triggers
Trigger push broadcast
Why VS Code Copilot?
GitHub Copilot Agent mode brings PushEngage data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 7 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
PushEngage in VS Code Copilot
PushEngage and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect PushEngage 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 PushEngage in VS Code Copilot
The PushEngage 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 7 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
PushEngage for VS Code Copilot
Every tool call from VS Code Copilot to the PushEngage MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my PushEngage API Key?
Log in to your account, navigate to Settings > Site Settings > API Keys, and copy your unique high-fidelity API Key.
Can I check subscriber analytics via AI?
Yes! The list_pushengage_subscribers tool allows your agent to retrieve high-fidelity profile metadata and engagement history for your audience.
How do I list my subscriber segments?
Use the list_pushengage_segments tool to retrieve the complete high-fidelity directory of audience segments along with their unique identifiers.
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.