"How to set up a local environment" matching MCP tools:

• oruk_analyze_speechA

  oruk SpeechA

  Transcribe English audio AND score how it was said in one call: transcript, tagged transcript, selected scores from 15 emotion and 16 speaking-style labels, and time-local segments. Use this when the user cares about both the words and the delivery — meetings, support calls, interviews, voice notes. Accepts wav/flac/mp3/m4a/ogg/webm. Up to 30 MB via audio_url or 8 MiB decoded via audio_base64; up to 60 minutes of English speech. Returns compact summaries by default. For words only use oruk_transcribe_audio; for tone only use oruk_analyze_tone.

  ConnectorNo auth

• dynomatix_get_positionA

  DynomatixA

  Read one job posting in full: responsibilities, requirements and how the role is set up. Returns the posting's own markdown, frontmatter included — the title and canonical URL it opens with are the citation to quote when you tell someone about the role. Call dynomatix_list_open_positions first to get a valid slug; a slug that is not currently open is refused rather than guessed at.

  ConnectorNo auth

• delete_containerA

  Cycle MCPA

  PERMANENTLY delete a container on Cycle. This is IRREVERSIBLE: it destroys the container, every one of its instances, and any data on stateful local instances. This tool is two-step by design and NOTHING is deleted on the first call: 1. Call without confirm. The container is resolved and the response describes exactly what would be destroyed — name, ID, environment, when it was created, and how many instances exist, their state, and which servers they run on. Present ALL of those details to the user verbatim. 2. Only after the user explicitly approves deleting that specific container, call again with confirm:true and container set to the exact 24-char hex ID from step 1 (names are not accepted with confirm — the ID binds the deletion to what the user approved). Never set confirm:true unless the user has just approved this exact deletion; a general instruction like "clean up the environment" is not sufficient. Containers with deletion protection (lock) cannot be deleted until unlocked; reconfigure_container with lock:false lifts it, which is itself a change the user must approve.

  Connector

  Destructive

  API key

• delete_environmentA

  Cycle MCPA

  PERMANENTLY delete an environment on Cycle and EVERYTHING in it: all containers and their instances (including data on stateful instances), all virtual machines and their disks, all scoped variables, and the environment's service containers (discovery, VPN, load balancer). This is IRREVERSIBLE. This tool is two-step by design and NOTHING is deleted on the first call: 1. Call without confirm. The environment is resolved and the response inventories exactly what would be destroyed — the environment's name, ID, and creation date, every container with its instance count, instance totals and the servers they run on, every VM, and every scoped variable. Present ALL of those details to the user verbatim. 2. Only after the user explicitly approves deleting that specific environment and its full contents, call again with confirm:true and environment set to the exact 24-char hex ID from step 1 (names are not accepted with confirm — the ID binds the deletion to what the user approved). Never set confirm:true unless the user has just approved this exact deletion; a general instruction like "clean things up" is not sufficient. To delete a single container instead, use delete_container.

  Connector

  Destructive

  API key

• sales_settings_numbering_readA

  Simpler.AsiaC

  How each numbered document type counts, one row each for invoice, quote, credit_note, debit_note and receipt: prefix, last_number (the highest number already used or skipped), next_number, and next_preview, the number the next one prints (this year's form, such as INV-2026-042). Copy next_preview, never build it. Change a next number, or a credit note, debit note or receipt prefix, with sales_settings_numbering_set; invoice and quote prefixes with sales_settings_upsert (prefix_set_with names the tool). A row with available false is not set up in this environment yet; unavailable_reason says why and what still works. Takes no arguments: any argument is refused with VALIDATION_ERROR.

  ConnectorNo auth

• research_keyword_volumeA

  tracetify-mcpA

  Google Ads (Keyword Planner) monthly search volume, CPC, competition, 12-month trend and keyword difficulty (0–100, DataForSEO Labs) for up to 10 keywords in one call. Use when the user asks how often something is searched or how hard it is to rank, or to size a keyword before writing a page. Omit location_code for worldwide volume (difficulty is then computed for the US), or pass a market code for one country. Costs credits; the same keyword set re-queried within a week is free.

  ConnectorNo auth

• list_monitorsA

  RoutebaseA

  List the monitors of a project with their current status. Set grouped to see them as an environment → spec tree the way the sidebar shows them (paging does not apply then). Set includeStats to add 24h uptime, p95 latency and the response-time sparkline per monitor. Use this to browse monitors or find a monitor id; for one monitor with its checks use get_monitor. Requires project context.

  ConnectorAPI key

• list_app_variablesA

  mcpA

  The NAMES of the environment variables of a hosted app or bot, and nothing else. Values are never returned by this tool, not even in part and not even to the owner: they are bot tokens, API keys and database passwords, and an assistant does not need them to work on an app. To read a value, open the Environment tab of the app in the panel. Use this to check whether a variable the app needs is set, and set_app_variables to add, change or remove one. The credentials of a bundled one-click database are written by FadeHost and kept in step on every save, so they appear here but cannot be changed or removed. Needs the app id (bot_...) from list_bots and full access to it, the same as the panel Environment tab.

  ConnectorNo auth

• cycle_control_environmentA

  Cycle MCPA

  Start or stop a Cycle environment. Starting brings up the environment's service containers: discovery (the environment's private DNS), scheduler, and — only once the environment has a public container — the load balancer. Containers in an environment cannot resolve each other by hostname until discovery is running — start the environment BEFORE deploying or setting up multi-container applications in it. Starting an already-live environment is safe and restarts any stopped services. Each service is itself a container and can be started or restarted individually with cycle_control_container using its container id. Stopping an environment stops its services AND every container in it — treat it as highly disruptive. Both actions are mutations: confirm with the user before calling. Waits up to wait_seconds for the job and returns the environment's state.

  Connector

  Destructive

  API key

• delete_virtual_machineA

  Cycle MCPA

  PERMANENTLY delete a virtual machine on Cycle. This is IRREVERSIBLE: it destroys the VM and its local volumes, including the base (boot) volume and everything the guest OS wrote to them. A running VM is powered off, not shut down gracefully. This tool is two-step by design and NOTHING is deleted on the first call: 1. Call without confirm. The VM is resolved and the response describes exactly what would be destroyed — name, ID, identifier, state, image, when it was created, and its volumes. Present ALL of those details to the user verbatim. 2. Only after the user explicitly approves deleting that specific VM, call again with confirm:true and virtual_machine set to the exact 24-char hex ID from step 1 (names are not accepted with confirm — the ID binds the deletion to what the user approved). Never set confirm:true unless the user has just approved this exact deletion; a general instruction like "clean up the environment" is not sufficient. VMs with deletion protection (lock) cannot be deleted until unlocked; reconfigure_virtual_machine with lock:false lifts it, which is itself a change the user must approve. Attached EXTERNAL (SAN) volumes are detached rather than destroyed, but local volumes are gone for good — if the guest holds data worth keeping, copy it out first (run_vm_command).

  Connector

  Destructive

  API key

• get_deployment_statusA

  Cycle MCPA

  Report where deployments (Cycle stacks and their builds) stand — the reconciliation tool when a deploy_application call was interrupted, timed out, or its response was lost. Read-only. Without arguments it lists recent stacks, newest first, each with its latest build. Pass 'stack' for one stack's detail including recent builds and their errors. Pass 'environment' to also see which of a stack's containers exist there — containers are created only by the final deploy step, so an empty container list on a live build means "generated but not yet deployed into this environment", not "failed". Each stack carries a derived 'phase': - generating: the latest build is still compiling/importing (new, building, importing, verifying, saving) — the pipeline is in flight, nothing is wrong. - deploying: the build is being deployed into an environment right now. - generated: the build is live; with 'environment' given, no containers from it exist there yet — the deploy step still needs to run. - deployed: the build is live and its containers exist in the given environment. - failed: the latest build ended with an error (shown on the build). To deploy a listed stack — reuse it in an environment, or continue an interrupted deployment — call deploy_application with stack_id set to the stack's id: it deploys the latest usable build, or a fresh one with rebuild:true, and picks up from the build's current state. Never resubmit a deployment from scratch after a timeout; check here first.

  ConnectorAPI key

• set_envA

  spawnpointA

  Add, update, or remove a spawnpoint project's environment variables without a redeploy: set upserts variables (everything not named is untouched), unset removes by name. Values are stored sealed, survive every later redeploy, and reach the app as its environment (~/app/.env); a running app is restarted with the new environment right away, and a sleeping project is woken to apply it, so expect the call to take a few seconds. During a deploy in progress the change is saved and applies when that deploy finishes; a project whose deploy failed stores it for its next deploy; a terminated project only stores it, and a new deploy under its name does not inherit it. The note says which happened, and none of these is a failure. deploy_project's env parameter feeds the same store, so pass env at deploy time when you have it and use this tool to change a variable on a live app. Returns the variable names now set; values are write-only and never returned. Never hardcode a secret into a project file; set it here instead. Refused on a static site, which runs nothing that could read a variable.

  Connector

  Destructive

  API key

• create_scheduleA

  RuncrateB

  Schedule an instance or a job to start later: once at run_at, or on a recurring cron in a timezone. Give exactly one of run_at or cron. spec is the launch itself, with the same fields as creating an instance (kind instance) or running a job (kind job). ALWAYS set spec.max_runtime_minutes: it is required, and the machine is stopped (billing ends) when it runs that long. A schedule fires within about 2 minutes of its time, in the current environment, and bills like a launch made then. Each run launches as you through this agent sign-in: if the sign-in ends (signed out or revoked), the schedule is paused with last_status credential_revoked. Recurring runs must be at least 15 minutes apart, and an environment holds at most 50 schedules (200 per workspace). Env values in spec (env, env_vars) are write-only: list_schedules shows only their names (env_keys). launch_script and startup_commands are shown to everyone in the environment by list_schedules; keep tokens in the environment secrets (set in the dashboard). Returns the schedule with next_run_at. Use list_schedules to see last_status and last_error after it fires, update_schedule to pause, resume or retime it, and run_schedule_now to try it at once.

  ConnectorAPI key

• telegram_watch_messages

  Local MCPA

  Asks Local MCP to tell this session when new messages arrive in chosen Telegram chats, so you do not have to keep calling telegram_read_messages. set needs `account` and `chats`. Local MCP checks every 300 seconds (delivery "poll"), so a notice can come about 5 minutes after the message. Each notice is a notifications/claude/channel message to this session with platform, account, chat, count, max_id and event_id, never the text: read the chat with telegram_read_messages. A notice can repeat: ignore an event_id you already saw. Watching starts now; read the chats once to catch up. It ends with this session. Only AI client builds certified to show these notices can set it; any other gets delivery "unsupported" and nothing is set up.

  ConnectorOAuth

• backup_createA

  TermalinA

  Make an encrypted backup of one of the user's servers now, through Termalin's backup job for that server, and wait for it (up to about a minute; a longer one keeps running and shows up in backup_list). Call it BEFORE a risky change — a migration, a config rewrite, a bulk delete — and say so in 'label'. The server needs a backup job set up in the Termalin cabinet (that is where the owner chooses the paths and the encryption key); without one this tool explains how to add it. Uses the owner's storage quota.

  ConnectorNo auth

• malware_get_templateA

  website-searchA

  Get Lenny Zeltser's malware analysis report template. The report covers Executive Summary, Sample Snapshot, Malware Family Identification, Component Inventory, Runtime Requirements, Sources, Capabilities, Indicators of Compromise, Analysis Details, What We Don't Know, optional Infection Vector, optional Detection Engineering, About this Report, Appendix: Analysis Environment, and optional Appendix: Analysis Scripts. This server never requests your sample, analysis notes, or indicators and instructs your AI to keep them local—guidelines and the report template flow to your AI for local analysis.

  ConnectorNo auth

• agent_statusA

  MERX - TRON Resource ExchangeB

  Get a snapshot of your agent payment service: registered TRON address, count of pending payment requests (request_payment), active address watches (watch_address), and outstanding invoices (create_invoice). Use this right after register_agent to confirm the agent is set up, or any time you want to see how much in-flight activity your agent has. Auth required (API key) and agent must be registered first via register_agent.

  ConnectorNo auth

• get_vessels_bulkA

  Datalastic Vessel Tracking & Maritime IntelligenceA

  Return the current position and basic information for many vessels in a single call — supply any mix of MMSI, IMO and UUID lists, up to 100 identifiers in total. Each result has the same fields as get_vessel. Only successfully found vessels are returned (the response includes how many were found). Use this instead of many get_vessel calls when looking up a known set of vessels; for a single vessel use get_vessel.

  ConnectorNo auth

• review_gapA

  Moonlings — Local Business IntelligenceA

  Compare a local business's Google rating and review count against the top same-category rivals nearby, with the gap math done: who leads, the rating delta, the review-volume ratio, and a verdict (leading / rated_equal_or_better_but_outreviewed / trailing). Live Google Maps lookup at call time. Call this when a user wants to know how a business's reviews stack up against local competitors. Takes a few seconds. Price: $0.39 per delivered comparison.

  ConnectorNo auth

• list_group_envsA

  seekrit — secrets for agentsA

  List the environments belonging to one shared GROUP — a group holds a separate value set per slug, so its `production` differs from its `staging`. Use this when you already have a group and want its own environments; use list_envs for an application's, and list_env_groups to see which groups an application environment pulls from. Returns Environment rows with `groupId` set: [{ id, name, slug, groupId, createdAt }].

  ConnectorNo auth

• delete_secretA

  seekrit — secrets for agentsA

  Delete a secret from an environment, discarding its ciphertext and every version. Irreversible — restore_secret CANNOT bring it back (that only rolls back within a surviving secret's history), and re-creating it means setting the value again on the local crypto plane. Prefer restore_secret to undo a bad write. Confirm intent before calling. Returns { ok, name } — or { ok, queued: true, changeRequestId } if the environment requires approval, in which case NOTHING was deleted until a human approves.

  Connector

  Destructive

  No auth