Customer beta · controlled rollout pending
Command-line interface

Coldvio, from any terminal.

Use predictable commands to inspect CRM, campaigns, actions, posts, trends and your voice profile. Built for customers, scripts and coding agents—with browser login and explicit confirmation for consequential work.

Works with: Claude · Codex · GitHub Copilot · VS Code · stdio MCP clients
coldvio
$ npx -y @coldvio/[email protected] login
✓ Browser authorization complete

$ npx -y @coldvio/[email protected] campaigns list --status running --limit 2
{
  "campaigns": [
    { "id": "8fa2…", "status": "running", "name": "Nordic founders" }
  ]
}

$ npx -y @coldvio/[email protected] actions list --status awaiting_approval --limit 5
1
customer login
17
agent-ready operations
JSON
for scripts and agents
What you can do

A practical control surface for your LinkedIn pipeline.

The CLI exposes the same customer-safe contract as MCP, with commands that are easy to inspect, pipe and automate.

See what needs attention

Check account summary, campaign state, pending approvals, content drafts and CRM follow-ups from one terminal.

Compose without sending

Generate LinkedIn or email drafts in the customer’s voice. Credit-spending commands require an explicit `--yes`.

Use it in agent workflows

Stable exit codes and structured output make the CLI useful from Claude Code, Codex, Copilot and shell scripts.

Set up

One install path. Human-readable by default.

Use npx for an exact version without a global install. The same browser login powers both direct CLI commands and the local MCP server.

Authenticate in the browser

The terminal never asks for the customer’s Coldvio password.

Inspect before acting

Use narrow list and get commands to resolve exact IDs and current state.

Confirm one bounded action

Consequential commands require `--yes`; then verify the result with a read.

Copy this to your coding agent
Set up the Coldvio CLI for me.

1. Check that Node.js 24 or newer is installed.
2. Run `npx -y @coldvio/[email protected] login` and wait while I sign in.
3. Run `npx -y @coldvio/[email protected] status`.
4. Show me the available commands, but do not run any write, generation or approval command.
The package is pinned to 0.1.0 so the setup stays reproducible. It becomes installable when the controlled customer rollout publishes the package.
Customer access by design

An agent connection should not become a master key.

Coldvio uses a dedicated customer Agent API, purpose-bound credentials and confirmation at the points where work changes state, spends credits or can reach LinkedIn.

Customer identity

The customer signs in with their own Coldvio account and reviews the requested access.

Tenant isolation

Every API query is scoped server-side to the signed-in customer—not to an ID supplied by the agent.

Purpose-bound access

Dedicated agent routes reject dashboard and browser-extension sessions.

Explicit confirmation

CRM writes, generation, approvals and rejections require confirmation for that exact operation.

Go deeper

From first login to production-safe patterns.

Explore product guides, exact client configuration, all 17 tools, the OpenAPI contract, security boundaries, use cases and troubleshooting in Coldvio Docs.