Bring Pitch Deck Analysis
to Cursor
Learn how to connect DeckMatch to Cursor and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the DeckMatch MCP Server?
Connect your DeckMatch (now AlphaLens) account to any AI agent and take full control of your venture capital deal flow and startup analysis workflows through natural conversation.
What you can do
- Deck Orchestration — Submit pitch deck URLs (PDF, PPTX, DocSend) programmatically to trigger automated data extraction and high-fidelity analysis
- Investment Intelligence — Programmatically generate professional investment memos and retrieve AI-driven triage results, including problem/solution and business models
- Semantic Discovery — Use the AlphaLens search engine to find startups matching specific strategic criteria and identify market signals directly through your agent
- Portfolio Monitoring — Access your complete directory of analyzed decks and monitor triage statuses to maintain perfectly coordinated deal flow pipelines
- Operational Monitoring — Check API health status, retrieve audit logs, and manage organization tags to maintain high-fidelity records of your investment activity
How it works
1. Subscribe to this server
2. Retrieve your API Key from your DeckMatch/AlphaLens dashboard settings
3. Start analyzing startup decks and searching your portfolio from Claude, Cursor, or any MCP client
No more manual data entry for every deck. Your AI acts as your dedicated investment associate and portfolio coordinator.
Who is this for?
- Venture Capitalists & VCs — instantly retrieve triage summaries and check startup metrics using natural language commands
- Investment Associates — automate the generation of investment memos and track deal statuses without leaving your workspace
- Accelerator Managers — monitor incoming applications and search for relevant startups through simple AI queries
Built-in capabilities (12)
Remove pitch deck
Create investment memo
Get connectivity info
Get AI triage results
Get audit trail
Get full submission info
Get data sources
List available tags
List all analyzed decks
Find similar startups
Submit a deck for AI analysis
Label a submission
Why Cursor?
Cursor's Agent mode turns DeckMatch into an in-editor superpower. Ask Cursor to generate code using live data from DeckMatch and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
DeckMatch in Cursor
DeckMatch and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect DeckMatch to Cursor 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 DeckMatch in Cursor
The DeckMatch 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 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor 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
DeckMatch for Cursor
Every tool call from Cursor to the DeckMatch 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 DeckMatch API Key?
Log in to your DeckMatch or AlphaLens dashboard and navigate to the Settings or API section to generate your secret key.
What deck formats are supported for analysis?
You can provide URLs for PDF and PPTX files, as well as direct view links from platforms like DocSend.
How does semantic startup search work?
The search_startups_semantically tool uses the AlphaLens engine to match your natural language query against a massive database of startups and their strategic metadata.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.