---
title: "corestack_ssh_login_get"
url: https://docs.corefinity.com/mcp/tools/corestack_ssh_login_get
type: tool
last_updated: 2026-11-13
feature: ssh-keys
related:
  - https://docs.corefinity.com/guides/sites/access-and-security/ssh-keys.md
---
# corestack_ssh_login_get

**Show my SSH login.** Shows your own SSH username (created on first ask, when your company allows it), your personal keys and each environment it works on, with its state and ready ssh command. Scope: read.

- Scope: `read`
- Runs as a task: no

## When to use it

Your own SSH username: created the first time you ask (when your company allows it), with your personal keys and every environment it works on, each with its state and the ready `ssh` command.

Each personal key's `delivery` says where it works: `applied` of `total` environments, `waiting` (environments where the key, or its removal, takes effect only at their one-time switch-over or a platform update), `waiting_platform_update` (how many of `waiting` wait for a platform update), `removed` (a key being removed: the environments it has already gone from; 0 otherwise) and `not_on_new_system` (environments that are not on the new system yet). A key with `state` `waiting` and `applied` 16 of 26 already works on 16; a removing key with `removed` 16 and `waiting` 10 has gone from 16 and leaves the other 10 at their switch-over.

`total` leaves out the environments that are not on the new system yet: they are counted in `not_on_new_system` only, and your username's state on each of them is `unmanaged` (use the username you have today there). Say "not on the new system yet", never that the key is waiting for them.

## Inputs

None.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {},
  "type": "object"
}
```

## Refusals

- The refusals every tool can answer: `invalid_arguments`, `tenant_mismatch`, `scope_required`, `pin_refused`, `rate_limited`, `temporarily_unavailable`, `internal_error` (corestack://guides/how-this-server-works).
- `switched_off`: SSH keys are not switched on for this object yet.
- `ssh_handle_missing`: your company has no SSH handle yet; ask Corefinity support.
- `ssh_login_unavailable`: no login can be issued for you.

## Example

```json
{
  "name": "corestack_ssh_login_get",
  "arguments": {}
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_ssh_login_get. (Show my SSH login.) Tell me what it returned.
```

## The same task elsewhere

- Guide: [SSH keys](https://docs.corefinity.com/guides/sites/access-and-security/ssh-keys.md)
