Overview
Work in Vruum Chat or your own AI agent, and learn the shared tools and revenue workflows.
Vruum runs the same revenue engine from two peer surfaces: the web app, and the AI harness you already use. Start a private conversation in Chat to analyze saved records, prepare an email, revise it, and review its exact delivery decision. Your connected agent can read and continue that same chat. In the web app you also set up and launch Objectives, work the ranked Priorities and the draft queue, review outreach and content, open Accounts, People, and Deals as full records, read Analytics, and manage Settings. In the harness the same people, accounts, deals, queues, objectives, research, marketing, content, tasks, team skills, and revenue truth are operated by conversation through MCP tools and Vruum skills. These pages explain setup, supported workflows, and the connection between both surfaces.
The clean mental model:
- Plugin: the easiest install path when your harness supports one. It packages MCP connection details, skills, and instructions.
- MCP: the live tool connection your agent calls to read and write Vruum.
- Skills: repeatable operating workflows like pipeline fill, outreach triage, engagement triage, and deal review.
- CLI: technical fallback for local setup, CI, local files, and debugging. Non-technical clients should not need it for day-to-day use.
Start here
- Quick Start — copy the install prompt, choose plugin, direct MCP, or technical CLI setup, then verify Vruum.
- Skills — the operating workflows agents should invoke.
Core references
| Page | What it answers |
|---|---|
| Plugin | Which harnesses can install Vruum as a plugin, and what to use when plugin rails are unavailable. |
| MCP | How to connect the hosted MCP server, authenticate, verify setup, and when to use the local CLI. |
| Skills | How to install, discover, invoke, and publish skills, plus the common operating workflows. |
| CLI Reference | The technical fallback command tree, --json, and exit codes. |
Workflow skills
Skills automate the workflows. Each skill page also shows the underlying MCP and CLI calls so an agent can inspect, verify, or recover.
| Workflow | Use when |
|---|---|
| Pipeline fill | Source, research, gate, import, and enroll qualified prospects. |
| Outreach triage | Review pending email and LinkedIn outreach drafts. |
| Engagement triage | Review LinkedIn warming, nurture, marketing engagement, and content drafts. |
| Deal triage | Review the pipeline; surface at-risk deals and the next action for each. |
Agent-readable docs
Agents should not scrape the rendered browser page. Use the text routes. There
is one site-level llms.txt and one site-level llms-full.txt; individual
pages are exposed as .md.
| URL | Purpose |
|---|---|
https://vruum.ai/llms.txt | Small docs index for discovery. |
https://vruum.ai/llms-full.txt | Full public docs corpus in one response. |
https://vruum.ai/docs/<page>.md | Any single docs page as clean Markdown. |
https://vruum.ai/docs/skills/<skill>.md | Any skill page as clean Markdown. |
Product boundary
Private Chat supports analysis and one email preparation or revision per message. Email delivery requires a separate decision on the exact current draft. A completed send does not establish a customer reply or revenue result.
Work, Objectives, and record pages remain available for their supported operations. Connected-agent skills support broader revenue workflows. Team conversation sharing, additional durable chat operations, and private connector context are still being developed.