Apps
Interactive views that some tools bring with them, which a client can show inside the chat.
On this page
An App is an interactive view that some tools bring with them. A client that supports MCP Apps shows it in the chat; any other client gets the same data as text.
Each App is listed at the end of this page with the tools that show it.
What it can reach
- An App holds no data of its own. It loads what it shows through the same tools, with your grant.
- Every call an App makes obeys the grant's scopes and pins, and appears in the activity log.
- An App loads nothing from other websites.
Without Apps support
Nothing is lost. Every tool that opens an App also returns its full result, so the assistant can read and summarise it.
All apps
Logs of a site or environment: a toolbar of source, range and filters over the lines, with expand, load older, copy and share with the agent.
Shown by corestack_logs_query.
CPU, memory and storage of a site or CoreCluster over a range, each chart with its limit and a table twin.
Shown by corecluster_usage_get, corestack_site_usage_get.
A smoke test's verdict: each path's status, timings and redirects, and the errors the site's logs showed.
Shown by corestack_site_smoke_test.
Choose a site or one of its environments, by search, kind or CoreCluster, and hand the choice to the agent.
Shown by corestack_site_list.
See who can connect to an environment over SSH, check your own address, add it at the level you choose and remove addresses.
Shown by corestack_firewall_list, corestack_firewall_my_ip_check.
Follow a range sent to Corefinity for approval: waiting, approved or rejected with the reason.
Shown by corestack_firewall_range_request.
Turn HTTP authentication and maintenance mode on or off for a CoreStack or CoreCluster environment, and see which addresses skip them.
Shown by corestack_firewall_web_access_get.
An environment's scheduled tasks (crons): the built-in task and your own, with their schedules, next and last runs — add, edit, turn off and remove them, and follow each change until it is applied in the site.
Shown by corestack_crons_get.
The 4-hour window (UK time) routine maintenance happens in, for a website, a CoreCluster's default or your company's default: where it comes from, the next slot and what is queued. Move it, see what a new start hour moves before you save, or go back to the default.
Shown by corestack_maintenance_window_get, corecluster_maintenance_window_get, corestack_company_maintenance_window_get.
The next seven days of maintenance for your websites: each one's slot and what is queued in it, with anything outside a website's own window marked.
Shown by corestack_maintenance_upcoming_list.
How to connect to one environment and who can log in with which keys: your username's and web's commands, the host keys, every key with where it comes from — add your key, remove one by typing its fingerprint, keep a key from the old shared list.
Shown by corestack_ssh_keys_list.
Your own SSH username, your personal keys and every environment it works on, with each one's state — add or remove a personal key, copy the ssh command or a ~/.ssh/config block.
Shown by corestack_ssh_login_get.
An environment's SSH host-key fingerprints and known_hosts lines — rotate them (staged or now), finish or cancel a staged rotation by typing the environment's name, and follow its progress.
Shown by corestack_ssh_host_keys_get.
The keys from the old shared web list that stop working at the cut-off, per environment with last use and CI hints — keep the ones you still use (at the level you choose) or remove them.
Shown by corestack_ssh_legacy_list.
Choose the application version for a new site: the platform, Magento's edition, every line you can create with its lifecycle and security end date, PHP and MariaDB for the line, then tell the agent which to create.
Shown by corestack_app_versions_list.
What a site runs and how long it is supported: the application and edition, the version it was created for and the one detected, its line's lifecycle with today marked, PHP and MariaDB against the line's range, and the next step.
Shown by corestack_site_app_version_get.
Your sites whose application version gets security fixes only or has ended, ended first: each with its version, the end date and the days left. Tick sites and tell the agent which to work on.
Shown by corestack_app_versions_attention_list.
A Magento 2 site's Varnish full-page cache: status and version, hit ratio, requests, cached objects, page storage, evictions and backend fetches over the last hour, day or week, the recent purges, and a sheet to purge everything, by tag, by address or by pattern.
Shown by corestack_varnish_get.