Bring Member Engagement
to VS Code Copilot
Learn how to connect Hullo to VS Code Copilot and start using 6 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Hullo MCP Server?
Connect your Hullo account to any AI agent and manage member communications through natural conversation.
What you can do
- Member Management — List all members, create new member profiles with contact details, and inspect individual member records
- Direct Messaging — Send messages to members with customizable content and message types
- Conversation Tracking — Browse all conversations and inspect individual threads with full message history
How it works
1. Subscribe to this server
2. Enter your Hullo API Key from your account settings
3. Start managing communications from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Community Managers — send messages, manage member profiles, and track conversations without switching to the dashboard
- Customer Success Teams — communicate with customers, onboard new members, and review conversation histories
- Operations Teams — manage member databases and automate communication workflows through AI
Built-in capabilities (6)
Pass member data as a JSON string. Create a new member
Get conversation details
Get member details
List all conversations
List all members
Pass message data as a JSON string. Send a message to a member
Why VS Code Copilot?
GitHub Copilot Agent mode brings Hullo data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 6 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
Hullo in VS Code Copilot
Hullo and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Hullo 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 Hullo in VS Code Copilot
The Hullo 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 6 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
Hullo for VS Code Copilot
Every tool call from VS Code Copilot to the Hullo 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 messages to members through the AI agent?
Yes. The send_message tool sends a direct message to a member. Provide a JSON payload with the member_id, content (the message text), and type (message type). Use list_members first to find the member ID.
Can I view the full conversation history with a member?
Yes. Use list_conversations to see all active conversations, then get_conversation with a specific conversation ID to retrieve the full message thread including sender, timestamp, and content for each message.
Can I create new member profiles and manage their contact information?
Yes. Use create_member with a JSON payload containing first_name, last_name, email, phone, and other contact details. Use list_members to browse existing members and get_member to inspect a specific profile.
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.