New:Microsoft Teams Notifications Are Now Available in Socket.Learn more →
Get Started

@crelora/olsales-cli

Package Overview
Dependencies
Maintainers
2
Versions
8
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@crelora/olsales-cli

Onelence Sales Operator CLI & MCP Client for remote sales pipeline management and AI agent integration

latest
npmnpm
Version
1.0.7
Version published
Weekly downloads
54
14.89%
Maintainers
2
Weekly downloads
 
Created
Source

Onelence Sales CLI (@crelora/olsales-cli)

Operator CLI and Model Context Protocol (MCP) server for remote sales pipeline management, outreach staging, attention feeds, and AI agent integration.

Installation

Method 1: Direct Git Installation (Private & Free)

Install directly from your private GitHub repository on any machine:

npm install -g https://github.com/crelora/onelence-sales#subdirectory=packages/cli

Method 2: Public Scoped NPM Package

Or install via NPM / npx:

# Run directly without installation (opens browser wizard at https://sales.onelence.com)
npx @crelora/olsales-cli login

# Or install globally
npm install -g @crelora/olsales-cli

Quickstart

1. Authenticate with Onelence Sales

Zero-configuration by default: URL and credentials are completely optional. Running olsales login with no arguments automatically opens the interactive browser wizard for https://sales.onelence.com.

# Recommended: Interactive browser wizard (zero flags needed; opens https://sales.onelence.com)
olsales login

# Optional: Connect to a custom or self-hosted server instance
olsales login --url=https://staging.sales.company.com

# Optional: Headless terminal login without browser (e.g. CI/CD or remote servers)
olsales login --email=user@company.com --password="YourPassword"

# Optional: Direct API token authentication
olsales login --key="your-api-key"

# Verify authenticated user, role, and server connection
olsales whoami

Credentials are saved securely in ~/.olsales/config.json with user-only (0o600) file permissions.

Commands Overview

Attention & Focus Feed

# High-priority focus summary
olsales focus summary

# Leads requiring urgent response (in Markdown)
olsales focus list --bucket=needsReply --markdown

# Leads due for follow-up
olsales focus list --bucket=followUpDue

Lead Investigation & Pipeline

# Search leads
olsales lead search "Fintech" --stage=qualified --min-score=80

# View lead profile and conversation history
olsales lead get awin:12345 --history --markdown

# Advance lead stage
olsales lead stage awin:12345 engaged --notes="Spoke with VP of Partnerships"

# Schedule a follow-up
olsales lead follow-up awin:12345 3 --notes="Check on contract review"

# Snooze lead for 7 days
olsales lead snooze awin:12345 7

Email Outreach & Dry-Run

# Preview / Dry-run a reply
olsales lead reply awin:12345 --text="Hello team, following up on our proposal." --dry-run

# Send email reply with library attachment
olsales lead reply awin:12345 --text="Attached is our pitch deck." --doc=deck_v2

Emergency Controls

# Check emergency pause status
olsales pause status

# Halt all outbound dispatches
olsales pause enable --reason="Server maintenance"

# Resume operations
olsales pause disable

MCP Server Integration for AI Agents (Claude Desktop, Cursor, Cline)

Remote HTTPS (preferred for Cursor, Hermes, OpenCode, Codex, ChatGPT)

https://sales.onelence.com/mcp

Bearer token from olsales login. ChatGPT web uses OAuth against the same URL (Developer mode connector).

Codex example:

[mcp_servers.olsales]
url = "https://sales.onelence.com/mcp"
bearer_token_env_var = "OLSALES_API_KEY"

Stdio

Add this to your claude_desktop_config.json or Cursor MCP settings:

{
  "mcpServers": {
    "olsales": {
      "command": "olsales",
      "args": ["mcp"]
    }
  }
}

Or run via npx:

{
  "mcpServers": {
    "olsales": {
      "command": "npx",
      "args": ["-y", "@crelora/olsales-cli", "mcp"]
    }
  }
}

FAQs

Package last updated on 17 Sep 2026

Related posts