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

@serviceagent/cli-dev

Package Overview
Dependencies
Maintainers
1
Versions
1
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@serviceagent/cli-dev

ServiceAgent CLI - OAuth CRM tools, local MCP bridge, embeddings, agents, and integrations

latest
Source
npmnpm
Version
1.1.0
Version published
Weekly downloads
7
-95.6%
Maintainers
1
Weekly downloads
 
Created
Source

@serviceagent/cli-dev

npm version npm downloads License: MIT

Authenticated developer CLI for the ServiceAgent platform — API-key and token management, knowledge-base search and embedding, AI agent CRUD, integrations, and workspace sync. The binary is sa.

npm install -g @serviceagent/cli-dev
sa auth                                  # store credentials locally
sa search-kb "refund policy"             # search the knowledge base
sa agents list                           # list AI agents
sa embed file ./policies.md              # embed local files into the KB
sa sync                                  # sync local config with the platform

Two ServiceAgent CLIs — pick the right one

PackageBinaryWhat it does
@serviceagent/cliserviceagentScaffolder. Drops <Chat />, <CalendarBooking />, <VoiceAgent />, webhook routes, and Cursor/AGENTS rule files into any project. No login.
@serviceagent/cli-dev (this package)saDeveloper CLI. Authenticated platform operations — API keys, embeddings, agents, sync, integrations.

If you are an end user setting up ServiceAgent in your app, you almost certainly want @serviceagent/cli.

Common commands

sa auth                           # interactive login (stores config in ~/.serviceagent)
sa keys list                      # list API keys
sa keys create --name "ci"        # mint a new API key
sa search-kb "query" --limit 10   # KB search
sa embed file ./doc.md            # embed a single file
sa embed url https://example.com  # embed a URL
sa agents list                    # list configured AI agents
sa agents create --name "Sales bot" --prompt "..."
sa integrations list              # list configured integrations
sa sync                           # sync local config files with platform

Run sa --help or sa <command> --help for the full reference.

Authentication

Either set credentials via sa auth (writes to ~/.serviceagent/config.json) or pass them inline:

sa --api-key <key> agents list
sa --token <jwt>   agents list
sa --api-key <key> --base-url https://api.serviceagent.com agents list

Pairs with

@serviceagent/cli · @serviceagent/sdk · @serviceagent/react · @serviceagent/nextjs · @serviceagent/aiva-sdk · @serviceagent/mcp (Cursor / Claude Desktop / Windsurf).

License

MIT

Customer CRM CLI (1.1.0)

This package also ships sa-crm for customer workflows using the hosted OAuth MCP gateway. It has a separate browser login and private credential store; sa credentials are not automatically reused. The hosted production endpoint supports this release.

sa-crm auth login --scope "leads:search tasks:create tasks:list"
sa-crm auth status --json
sa-crm tools list
sa-crm mcp setup --client gemini
sa-crm mcp serve
sa-crm auth logout

sa-crm mcp serve bridges local stdio clients to the same customer CRM tools as the hosted endpoint. It keeps stdout as JSON-RPC and diagnostics on stderr. Use sa-crm mcp setup --client stdio for its configuration. The endpoint defaults to https://process.serviceagent.ai/v1/mcp; set SERVICEAGENT_API_URL to a different HTTPS origin for staging. A browser and a loopback callback are required for login.

Credentials live in ~/.config/serviceagent/crm.json (0600); this is a restricted file store, not an OS keychain. SERVICEAGENT_CRM_CONFIG overrides its location. Logout revokes the connection before deleting credentials. Supported workspace roles: active owner/admin. Registration defaults to read scopes; explicitly request and consent to write scopes.

For request retries, supply the same --idempotency-key on sa-crm tools call NAME --args JSON. Without an explicit key, the MCP session/request ID identifies only that invocation. See customer setup guide for client-specific instructions and rollout status.

Keywords

serviceagent

FAQs

Package last updated on 09 Sep 2026

Related posts