Drive your whole funnelfrom your agent.
KRTR is built MCP-first. Every operation the web app exposes is an agent-callable verb — so your dealflow becomes the substrate your agents read, score, and act on, not a dashboard you check.
Anonymous agents stream into the KRTR core. No partner logos — the substrate is the point.
Your deals, reports, signals, and funnel are state your agents read and write directly. KRTR is where the deal data lives; your agent is just one more client.
A Streamable-HTTP MCP server exposes the same verbs the web app uses. Screen a funnel, run a report, drop a signal, draft a memo — from Claude, Cursor, or your own fleet.
Auth, quota, and scoring live inside the operations, not the transport. An agent can't bypass a limit the web enforces — the rules hold whichever way you connect.
What you can hand to an agent
These aren't roadmap promises — every verb below is live on the MCP surface today. Describe the outcome; the agent calls the same operations the app does.
Watch the pipeline continuously
Point a long-running agent at your funnel. It polls running jobs, surfaces newly-scored deals, and pings you the moment something crosses your bar — no tab to keep open.
"Every morning, list deals that scored 80+ overnight and summarize what changed."
Re-screen the whole funnel against a new thesis
Thesis shifted? Have the agent batch-screen every open deal through your updated lens in one pass, then re-rank — instead of re-opening each deal by hand.
"Re-screen my whole funnel for infra-AI with a hardware moat and show me the new top 10."
One-pass funnel screening through your own lens
Drop a batch of decks; the agent triages all of them through your calibrated thesis at once, returning a ranked shortlist with the reasoning — the screening wedge, automated.
"Screen these 40 inbound decks and give me the 6 worth a first call, with why."
Cross-tool — KRTR alongside Slack, Gmail, your CRM
Because KRTR speaks MCP, the same agent that screens a deal can post the shortlist to Slack, draft the intro in Gmail, and log the disposition to your CRM — one prompt, many tools.
"Screen this deck, post a verdict to #dealflow, and draft a pass note if it's below my bar."
KRTR is self-describing. An agent says “Initiate KRTR” to learn who it's acting as and what it can do, then asks for a workflow or learns a section on demand — so it always knows the right next move without you wiring prompts.
Three steps to your agent on KRTR
No SDK, no glue code. If your client speaks MCP, you're a sign-in away.
- 1
Add KRTR to your MCP client
In Claude Desktop, Cursor, or any MCP-capable client, add KRTR as a server. It's a standard Streamable-HTTP MCP endpoint with OAuth — your client walks you through sign-in; no API keys to paste.
https://krtr.ai/api/mcp - 2
Say "Initiate KRTR"
On the first message, ask the agent to initiate KRTR. It learns who you are (founder, investor, or firm), what role it's acting as, and the operations available to you — the agent primes itself.
Initiate KRTR - 3
Ask for your first moves
Let the agent suggest where to start, or go straight at it — list your deals, screen your funnel, run a report. From here it's plain language; KRTR maps it to the right verb.
What are my first moves?
Ready to join the first collective intelligence platform for venture capital?
160K+ investors · 50K+ firms · Intelligence that compounds
Already have an account? Sign in