Bring Demo Automation
to VS Code Copilot
Learn how to connect CONSENSUS 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 CONSENSUS MCP Server?
Connect your Consensus account to any AI agent and take full control of your interactive video demo and buyer intelligence workflows through natural conversation.
What you can do
- DemoBoard Orchestration — List and manage your active DemoBoards programmatically, retrieving detailed metadata about leads and stakeholder engagement
- Demolytics Intelligence — Access real-time analytics to understand which sections of your automated demos are being watched, skipped, or shared by prospects
- Invitation Tracking — Programmatically monitor sent demo invitations and track outreach performance to coordinate perfectly timed sales follow-ups
- Asset Discovery — Retrieve a complete directory of all available interactive demos and assets in your library to maintain high-fidelity sales enablement
- Team Visibility — Access directories of account users and roles to maintain an organized sales team structure and permission oversight
How it works
1. Subscribe to this server
2. Retrieve your API Key and Secret from Consensus (Settings > Integrations > API Credentials)
3. Start managing your interactive sales pipeline from Claude, Cursor, or any MCP client
No more manual status checking of individual demo links. Your AI acts as your dedicated sales associate and demolytics coordinator.
Who is this for?
- Sales SDRs & AEs — instantly retrieve lead engagement summaries and monitor who is watching your demos using natural language commands
- Sales Operations — track overall demo performance and team usage metrics without leaving your communication tools
- Marketing Leads — monitor interactive asset popularity and buyer intent signals through simple AI queries
Built-in capabilities (6)
Get DemoBoard details
List all DemoBoards
List analytics for demos
List all available demos
List sent demo invitations
List all account users
Why VS Code Copilot?
GitHub Copilot Agent mode brings CONSENSUS 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
CONSENSUS in VS Code Copilot
CONSENSUS and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect CONSENSUS 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 CONSENSUS in VS Code Copilot
The CONSENSUS 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
CONSENSUS for VS Code Copilot
Every tool call from VS Code Copilot to the CONSENSUS 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 Consensus API Key and Secret?
Log in to your account, navigate to Settings > Integrations > API Credentials, and generate a new set of keys.
What are Demolytics?
Demolytics provide deep insights into buyer engagement, showing exactly which parts of your interactive demos were most valuable to a prospect.
Can I see all invitations sent via AI?
Yes! Use the list_invitations tool to retrieve a complete history of demo invites sent from your account 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.