Bring Demo Automation
to Claude Code
Learn how to connect CONSENSUS to Claude Code 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 Claude Code?
Claude Code registers CONSENSUS as an MCP server in a single terminal command. Once connected, Claude Code discovers all 6 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where CONSENSUS data drives decisions without human intervention.
- —
Single-command setup:
claude mcp addregisters the server instantly. no config files to edit or applications to restart - —
Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks
- —
Claude Code runs headlessly, enabling unattended batch processing using CONSENSUS tools in cron jobs or deployment scripts
- —
Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features
CONSENSUS in Claude Code
CONSENSUS and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect CONSENSUS to Claude Code 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 Claude Code
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 Claude Code 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 Claude Code
Every tool call from Claude Code 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.
How do I add an MCP server to Claude Code?
Run claude mcp add --transport http "" in your terminal. Claude Code registers the server and discovers all tools immediately.
Can Claude Code run MCP tools in headless mode?
Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.
How do I list all connected MCP servers?
Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.
Command not found: claude
Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code
Connection timeout
Check your internet connection and verify the Edge URL is reachable
