leadt3ch

Joined on 2026-03-09

@pro-select/pros-cli (0.5.55)

Published 2026-08-16 07:14:31 +02:00 by leadt3ch

Set up this registry in your project .npmrc file:

@pro-select:registry=

To install the package using npm, run the following command:

npm install @pro-select/pros-cli@0.5.55

or add it to the package.json file:

"@pro-select/pros-cli": "0.5.55"

For more information on the npm registry, see the documentation.

pros-cli

Source package for the Pro Select pros CLI.

Purpose

This package is authored inside pro-select-harness.
It is intended to become the Windows-facing runtime used by Pro Select staff in a business working folder.
It is separate from the repo-local oma development workflow.

Current Scope

Inspect the active business workspace
Summarize the workspace in a Pro Select-specific way
Build an initial case-oriented deliverable package
Recommend a Mistral model for the current task
Configure Pros-managed MCP client entries for OpenCode and AnythingLLM
Verify MCP readiness with deterministic, read-only JSON results

Local Development

npm ci
npm run build
npm test
npm run cli -- --help

Manual MCP CLI Commands

Run the MCP commands from an initialized business workspace. The supported MCP clients are opencode and anythingllm. For OpenCode, the supported --include values are hubspot, microsoft-graph, qnap-mcp-assistant, docx-local, excel-local, and powerpoint-local. For AnythingLLM, only the provider includes hubspot, microsoft-graph, and qnap-mcp-assistant are supported; local Office includes are unsupported there. Pass multiple targets as a comma-separated list.

Configure

Preview first, then write only the client the user actually uses:

pros mcp configure opencode --include hubspot,microsoft-graph,qnap-mcp-assistant,docx-local,excel-local,powerpoint-local --dry-run
pros mcp configure opencode --include hubspot,microsoft-graph,qnap-mcp-assistant,docx-local,excel-local,powerpoint-local

pros mcp configure anythingllm --include hubspot,microsoft-graph,qnap-mcp-assistant --dry-run
pros mcp configure anythingllm --include hubspot,microsoft-graph,qnap-mcp-assistant

pros mcp configure ... --json resolves the comma-separated list into independent supported targets and returns one results[] entry per include, even when another target is blocked. It manages only Pros-owned MCP entries, preserves unrelated entries, and never writes provider secrets.

Verify

Canonical contract command:

pros mcp verify <opencode|anythingllm> --include <mcp[,mcp...]> --json

Optional flags:

--level configured|connected|function defaults to function.
--allow-live is required for provider-backed read-only function checks: hubspot, microsoft-graph, and qnap-mcp-assistant.
--json only selects machine-readable output; it never implies live provider consent.

Evidence levels in each result are independent:

configured: the target is present in the Pros-managed client configuration.
connected: the MCP server initializes and exposes connection evidence such as tools/list or the remote handshake.
functionVerified: the fixed target-specific read-only function check succeeded.

Local Office checks do not require network or --allow-live, but are supported only for OpenCode (not AnythingLLM):

pros mcp verify opencode --include docx-local,excel-local,powerpoint-local --json

Provider function checks require explicit live consent:

pros mcp verify opencode --include hubspot,microsoft-graph,qnap-mcp-assistant --allow-live --json
pros mcp verify anythingllm --include hubspot,microsoft-graph,qnap-mcp-assistant --allow-live --json

Without --allow-live, provider-backed function verification returns consent_required and sends no network request.

Example success JSON:

{
  "schemaVersion": 1,
  "command": "pros mcp verify",
  "client": "opencode",
  "status": "ready",
  "success": true,
  "exitCode": 0,
  "results": [
    {
      "include": "docx-local",
      "configured": true,
      "connected": true,
      "functionVerified": true,
      "status": "ready",
      "evidence": ["MCP initialize and read-only fixture inspection succeeded."],
      "nextAction": "No action required."
    }
  ]
}

Example consent-gated JSON:

{
  "schemaVersion": 1,
  "command": "pros mcp verify",
  "client": "opencode",
  "status": "consent_required",
  "success": false,
  "exitCode": 1,
  "results": [
    {
      "include": "hubspot",
      "configured": false,
      "connected": false,
      "functionVerified": false,
      "status": "consent_required",
      "evidence": ["Provider-backed function verification was not started because --allow-live was not provided."],
      "nextAction": "Retry with --allow-live only after explicitly consenting to the read-only provider check."
    }
  ]
}

Notes

Provider live checks are read-only and require explicit --allow-live.
Verification must redact credentials, OAuth artifacts, tokens, sensitive headers, sessions, provider payloads, and unsafe paths.

Dependencies

ID	Version
@modelcontextprotocol/sdk	^1.29.0
jsonc-parser	^3.3.1
mcp-remote	0.1.38
zod	^3.25.76

Details

npm

2026-08-16 07:14:31 +02:00

UNLICENSED

370 KiB

Assets (1)

pros-cli-0.5.55.tgz 370 KiB

Versions (61) View all

0.5.57

2026-08-17

0.5.56

2026-08-16

0.5.55

2026-08-16

0.5.54

2026-08-03

0.5.53

2026-07-23