Bring Conversational Commerce
to VS Code Copilot
Learn how to connect Blip to VS Code Copilot and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Blip MCP Server?
What you can do
- Send WhatsApp and Chatbot messages directly to your customers.
- Create, update, and retrieve detailed contact information.
- Monitor support tickets from Blip Desk and manage ongoing conversation threads.
- Analyze active conversations to trigger personalized workflows.
How it works
1. Log in to your Blip portal and access your bot's settings. 2. Copy the API Key from the Connection Information area. 3. Securely connect your agent to start managing Blip communications instantly.Who is this for?
Customer Support teams managing tickets, Marketing teams triggering proactive messages, and Sales professionals following up on leads via WhatsApp.Built-in capabilities (10)
Create or update a Blip contact
Delete a Blip contact
Get a Blip contact by ID
Get messages from a Blip thread
Get a Blip desk ticket by ID
List Blip contacts
List Blip conversation threads
List Blip desk tickets
Ping the Blip bot
Send a message to a Blip contact
Why VS Code Copilot?
GitHub Copilot Agent mode brings Blip data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 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
Blip in VS Code Copilot
Blip and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Blip 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 Blip in VS Code Copilot
The Blip 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 10 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
Blip for VS Code Copilot
Every tool call from VS Code Copilot to the Blip MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can the AI Agent manage ongoing Chatbot threads?
Yes, the agent can list active threads and retrieve their messages to understand the full context of a customer's conversation.
Is it possible to reply to customer support tickets on Blip Desk?
The AI agent can retrieve and analyze tickets from Blip Desk and send direct messages to the user via the send_message tool to assist with resolutions.
Can I use the agent to send automated WhatsApp notifications?
Absolutely. The agent can use the messaging capabilities to trigger plain text messages directly to phone numbers connected to your Blip router.
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.