revnos
v0.0.6
Published
Local-first GTM integration layer: 37+ providers, durable workflows, MCP server — runs on your machine, your keys.
Readme
revnos
Give your AI assistant real access to your GTM stack — locally, on your keys.
revnos is a local integration layer for 38 sales & marketing tools (HubSpot, Apollo, SendGrid, Slack, Gmail, Instantly, ZoomInfo…). Your coding agent — Claude Code or Codex — connects to it over MCP, discovers 500+ ready-made actions, and can write workflows that keep running on a schedule long after the conversation ends. Everything lives on your machine: credentials in an encrypted local vault, runs in a local SQLite journal, no SaaS in the middle.
Get started
You'll need Bun (curl -fsSL https://bun.sh/install | bash). Then, inside a project:
npx revnos init # detects your installed agents automatically — or pass --harness claude|codex|opencode|copilot|antigravity|claude-desktopThat installs the revnos skills + subagents and wires up the MCP server. Open your agent and start talking:
"Connect my Apollo account, then find 50 CTOs at fintech startups and verify their emails."
The first time a provider needs credentials, revnos opens a local connect page — paste an API key or click through OAuth once, and it's stored encrypted for good.
The part that's actually different
Most tool catalogs make your agent call APIs one at a time, every time. revnos lets the agent write a workflow instead — a small TypeScript file it registers with revnos:
"Every morning, pull yesterday's Smartlead replies and log them in HubSpot as deal notes."
The agent drafts the workflow, dry-runs it so you can see exactly what it would write before anything touches your CRM, and then schedules it. From that point on it runs as plain deterministic code — no tokens burned, no agent needed. If your laptop sleeps mid-run, revnos resumes where it left off: every step is journaled, retries back off politely, and failures are kept for you to inspect.
There's a little dashboard for all of it:
npx revnos ui # run history, step journal, logs, schedules, dry runsWhat's connected
CRM & sales: HubSpot, Outreach, Salesloft, Apollo, ZoomInfo, Lusha, Hunter.io, Snov.io, Warmly, Leadfeeder Email & outreach: SendGrid, Instantly, Smartlead, Lemlist, Mailshake, Woodpecker, Klenty, Reply.io, Brevo, Mailchimp, MailerLite, Klaviyo, ActiveCampaign, Gmail, Outlook Verification: ZeroBounce, NeverBounce, MillionVerifier, Bouncer, No2Bounce Everything else: Slack, Microsoft Teams, Google Calendar, Calendly, Chili Piper, Zapier, Make, n8n
Missing one? Ask your agent to build it — the connector-builder subagent writes new
connectors into ~/.revnos, live immediately, no restart.
How it works, in one breath
One process. A Bun app hosts the tool registry, the credential vault (AES-256-GCM, key auto-generated on first run), the durable runner (SQLite — journal, retries, crash resume, cron), and the MCP server your agent talks to. OAuth apps are bring-your-own — the connect page walks you through it. Nothing phones home.
Curious about the internals? docs/ARCHITECTURE.md walks
through every piece, and docs/WORKFLOWS.md covers
workflows-as-code.
Updating
npx caches aggressively, so grab fixes with:
npm install -g revnos@latestthen restart your agent session — the MCP server (and its tool list) lives for the
session, so new versions take effect on the next spawn. revnos serve prints a note
whenever a newer version exists, and npx revnos --version shows what you're on.
License
Apache-2.0. Use it, fork it, ship it.
