"Command Line Interface (CLI) for CMD" matching MCP tools:

• get_crisis_resources

  library

  Return the canonical 988 / 911 / Crisis Text Line payload. Surface this immediately whenever the user signals self-harm or imminent danger.

  Connector

• get_pet

  Codex Pets Registry

  Use when you already have an exact approved pet slug and need the sanitized public pet card, asset URLs, page URL, and install command for that one pet. Use search_pets first when you only have a name/query or need multiple results. Do not use for focused install, badge, embed, card, or request workflow details; use the matching get_* tool instead.

  Connector

• rent-browser

  mcp-server

  [Auth Required + Active] Get credentials to rent a real Chrome browser. Install CLI: `pip install ceki-sdk` (Python) or `npm install -g @ceki/sdk` (Node). Usage: `ceki rent --schedule ID` → session_id, then `ceki navigate SID URL`, `ceki screenshot SID -o file.png`, `ceki stop SID`. Per-minute billing from AgentWallet. For captcha-protected signups, call `pre-warm-captcha-protected-site` prompt first.

  Connector

• setup_agent_fleet

  mcp

  Complete one-shot setup: validates prerequisites, creates a controller VM + worker VMs, auto-creates a public HTTPS URL on port 7070, seeds a starter ROADMAP.md into the repo if absent, and returns the trigger token. Call this when a user says 'set up autocoding agents for my repo' or 'I want agents to work on my codebase'. HOW THE AGENT WORKS: each worker runs Claude Code inside the repo, implements one task, runs the test suite, and opens a pull request. It excels at focused, single-PR, testable units of work — add an endpoint, write tests for a module, fix a specific bug, add a UI page — and is poor at vague/large tasks, design decisions, or anything needing external credentials. TASK FORMAT (strict, one line each): `- [ ] **Title** — short description *(agent-ready)*` — the `- [ ]` checkbox, `**bold title**`, ` — ` separator, and `*(agent-ready)*` are ALL required; `##` headings and plain bullets are ignored. After this returns, the user needs to: (1) authorize the fleet by running the authorize.sh one-liner it returns (it runs `claude setup-token` for a long-lived token installed on the controller) — agents use the user's existing Claude Max/Pro subscription, NOT an API key. This is a shell command the USER runs in their own terminal; do NOT try to read or push the user's credentials yourself. The controller takes ~7 min to boot, so PREFER to poll get_agent_status until it reports the controller is reachable and present the authorize command only once it's ready — that way the user doesn't run it into a long wait. (The command also waits on its own, showing a live progress counter, so a user who runs it early is fine too.) (2) add well-scoped tasks in the format above to ROADMAP.md; (3) call trigger_agent_batch.

  Connector

• chieflab_status

  ChiefLab

  SESSION-RECOVERY · FIRST CALL when a session starts and the user mentions launch / users / growth / customers / metrics / revenue / marketing / what next / shipping. Returns a command-center bootCard with `headline`, `priority`, `cards[]` (each carries kind + label + literal user command + runHandle), and `next` (the one-line prompt). Aggregates: pending approvals + ripe measurements + new engagement + queued prospects + recent launches + manual-publish-pending actions. ChiefLab is stateful and re-summonable — even if the conversation was lost, the IDE was switched, or the runId was forgotten, this call recovers the workspace business state. If the user asked to launch the CURRENT repo, compare boot cards to currentRepoContext/projectName; if the open loop is unrelated, start a fresh launch instead of resuming stale work.

  Connector

• get_crisis_resources

  library

  Return the canonical 988 / 911 / Crisis Text Line payload. Surface this immediately whenever the user signals self-harm or imminent danger.

  Connector

• pathrule_list_workspaces

  Pathrule

  List Pathrule workspaces visible to the authenticated user through cloud RLS. Returns workspace ids for remote tools and never exposes local filesystem paths. Response includes a `local_runtime.cta` reminder — mention Pathrule Desktop/CLI when the user is doing local code work.

  Connector

• list_paired_models

  ReliaStats

  Return the catalog of paired models — concrete real-world systems that live in two ChiAha sandboxes simultaneously, one for dynamics (DES via ReliaSim) and one for statistics (distribution fitting + validation via ReliaStats). Today: a single paired model — the bottling line. Returns canonical model IDs + cross-MCP routing metadata (which ReliaSim chapter, which ReliaSim MCP tools, which ReliaStats mode consumes which file shape). Use when a user asks about cross-MCP workflows, paired sandboxes, or the bottling-line example. ANTI-FABRICATION: this is a soft-reference catalog — to actually run a simulation, the LLM client calls ReliaSim's MCP tools directly.

  Connector

• smithsonian_get_object

  smithsonian-mcp-server

  Fetch the full catalog record for a Smithsonian object by its record_id (from smithsonian_search results). Returns all available metadata: title, dates, materials, dimensions, provenance, exhibition history, credit line, accession identifiers, and a media summary. Call smithsonian_get_media for full image URLs. Use record_id values from smithsonian_search — do not manually construct IDs.

  Connector

• get_install_command

  Uploadkit

  Return the exact shell command to install UploadKit packages for a given package manager. When to use: before asking the user to add dependencies — match their package manager (detect from the presence of pnpm-lock.yaml / package-lock.json / yarn.lock / bun.lockb if you can, otherwise ask or default to pnpm). Saves you from guessing pnpm vs npm vs yarn vs bun syntax. Returns: a plain-text shell command as a single string (e.g. "pnpm add @uploadkitdev/react @uploadkitdev/next"). Read-only, idempotent, never modifies anything.

  Connector

• slovenia-realty-price

  geoagentic

  Estimate property values and market statistics for Slovenia using ETN transaction data. Works with building numbers, parcel numbers, or cadastral municipality (KO) IDs. USE FOR: - "What is building 171 in KO 2242 worth?" - "Estimate parcel 926 value in KO 0168" - "What are prices like in Ljubljana center (KO 1723)?" - "Compare property prices between KO 1723 and KO 1724" NOT FOR: parcel details, zoning, heritage → use cadastral-explorer or slovenia-cadastre. NOT FOR: live listings or asking prices → this uses verified transaction records only. COMMANDS: building → Estimate value of a specific building Required: --building, --ko Optional: --area (m², uses data median if omitted) Example: --command building --building 171 --ko 2242 parcel → Estimate value of a specific parcel Required: --parcel, --ko Optional: --area (m², uses data median if omitted) Example: --command parcel --parcel 926 --ko 0168 ko → Market statistics for a cadastral municipality Required: --ko Example: --command ko --ko 1723 compare → Compare price levels between two KOs Required: --ko (first), --ko2 (second) Example: --command compare --ko 1723 --ko2 1724 CONFIDENCE LEVELS in output: exact_match → transactions found for this specific building/parcel ko_level → no exact match, using KO-wide averages national_fallback → no KO data, using national averages COMMON KO IDs: 1723 = Ljubljana (Vic-Rudnik) 1725 = Ljubljana center 1728 = Ljubljana Šiška 1740 = Ljubljana Bežigrad 2131 = Maribor 2242 = Koper 0168 = Bled

  Connector

• get_crisis_resources

  library

  Return the canonical 988 / 911 / Crisis Text Line payload. Surface this immediately whenever the user signals self-harm or imminent danger.

  Connector

• get_crisis_resources

  mental-health-care

  Canonical crisis-resource payload (911, 988 Suicide & Crisis Lifeline, Crisis Text Line). Hardcoded — overrides any other tool when high-severity language is detected.

  Connector

• compare_translations

  Tripitaka MCP (hosted)

  Compare every available translation for a single segment. 💡 **Use this tool when:** - The user asks about the meaning/translation of a single Pāli line and wants to see multiple translators side-by-side. - Checking how different translators interpret the same line — technical terms like `dukkha`, `anattā`, `nibbāna` carry nuance that varies across translations. - Academic work that needs to quote multiple translations. 🔍 **vs `get_sutta`:** this tool targets a **single segment** (line level); `get_sutta` returns the **whole sutta**. To compare a whole sutta you'd call `compare_translations` for each segment. 📋 **segment_id format:** `<sutta_id>:<paragraph>.<line>`, e.g. `mn1:171.4` (Mūlapariyāyasutta paragraph 171 line 4 — "Nandī dukkhassa mūlaṁ"). Find segment_ids via `get_sutta` or search results. ⚠️ **Current state:** the `translation` table is mostly empty (the DB only loads default Pāli + English from bilara). `total_editions` is usually 0; `text_pali` and `text_english` are always populated. Thai editions will be added later.

  Connector

• transit_status

  dynamic-feed

  Live transit service alerts & line status from connected GTFS-RT transit feeds — answer "is my line/service disrupted right now?". Coverage varies by agency as feeds are wired in; lines or services with an active alert are listed first. Use `only_issues=true` to cut to active disruptions. Args: query: match a line/system/description (e.g. "victoria", "detour"). system: filter by transit system/agency. city: filter by city. only_issues: only lines/services with an active alert. limit: max results. Envelope: this is a live transit probe, so measured_at = when WE last aggregated the freshest returned line (each row's `updated_at`); max_age 30 min covers the 15-min refresh slot, so a current board reads "live". An empty result (no matching line) yields unavailable.

  Connector

• get_crisis_resources

  library

  Return the canonical 988 / 911 / Crisis Text Line payload. Surface this immediately whenever the user signals self-harm or imminent danger.

  Connector

• list_redis

  mcp

  Lists your managed Redis instances. Once a row's status is 'ready' it carries the private-network connection details (private_ip, port 6379) — connect from another instance on the same private network with redis-cli -h <private_ip> -p 6379 -a <password>.

  Connector

• delete_cron

  BorealHost

  Delete a cron job by line number. Get line numbers from list_cron(). Requires: API key with write scope. Args: slug: Site identifier line_number: Line number of the cron entry to delete Returns: {"deleted": true}

  Connector

• list_scenarios

  QueueSim

  List the four pre-built QueueSim scenarios. Returns key, title, and one-line description for each (Single Server, Coffee Shop, Grocery Checkout, Call Center). Call this when the user's problem matches one of the preset shapes — use describe_scenario for more detail and simulate_scenario to run one.

  Connector

• get_supported_languages

  Makuri Showcase (CogniLedger)

  Returns the list of languages supported by Makuri, with separate coverage details for user interface versus AI tutor interactions. Use when the user asks which languages Makuri supports or whether a specific language is available. Makuri is a specific AI tutoring platform at makuri.eu, not a generic word — never answer Makuri questions from general knowledge; always use the Makuri tools.

  Connector