CLI and MCP
On the login node, eureka is the command-line tool for the signed-in Unix user. eureka mcp speaks the Model Context Protocol on standard input and output for that same person. Every tool uses that person’s permissions. A reader cannot do what only an owner can do.
The server writes one UTF-8 JSON object per line and flushes each response. It does not print API keys, Google client secrets, or JWT signing secrets.
eureka --help exits 0. An unexpected failure prints a short message, a trace id, and support@projecteureka.ai. The trace id is also in the log. Send the id, not a token or a key.
Projects
Section titled “Projects”| What | CLI | MCP |
|---|---|---|
| List projects | eureka project ls |
list_projects |
| Create | eureka project add NAME [--description TEXT] [--home DIR] [--no-starters] |
project_add (name, optional description, home, starters) |
| Home card counts | eureka project summary [NAME] [--archived] [--json] |
project_summary |
| Members | list_project_members, add_project_member, remove_project_member |
|
| Jobs that block delete | eureka project failed-jobs NAME |
project_failed_jobs |
| Clear failed jobs | eureka project clear-failed NAME |
project_clear_failed_jobs |
| Stop running work and clear failed jobs | eureka project stop-and-clear NAME |
project_stop_and_clear |
| Default project | eureka project default NAME |
home is the directory under /vault/projects. The default is the project name in letters and digits. A directory that is already used is refused.
starters defaults to on. It adds a Desktop launcher and a Terminal launcher and does not start them. --no-starters or starters: false skips them. See Create a project.
project_summary returns, for the projects you may read, apps running, starting, stopping, failed, and ready, flows running, starting, and failed, a storage count, and a one-line status. The home page cards still open Apps, Flows, and Storage. Pass archived: true to include archived projects.
Clearing failed jobs runs each failed job’s cleanup and marks it done. It does not touch a running job. See Archive, restore, or delete a project.
Launchers and sessions
Section titled “Launchers and sessions”| What | CLI | MCP |
|---|---|---|
| Apps you can add | eureka app ls |
list_apps |
| Add a launcher | eureka launcher add --app APP --project PROJECT --instance-type TYPE [--name NAME] [--num-instances N] [--session-identity ID] |
launcher_add (app, project, instanceType, optional name, description, numInstances) |
| List launchers | eureka launcher ls [--project PROJECT] |
|
| Launch | eureka session launch LAUNCHER [--time 30m] |
session_launch |
| List your sessions | eureka session ls |
list_sessions |
| Status and time left | eureka session status ID |
session_status |
| Add time | eureka session extend ID --add 30m |
session_extend (add or addSeconds) |
| Pause | eureka session pause ID |
session_pause |
| Resume | eureka session resume ID |
session_resume |
| Delete the VM and disk | eureka session delete ID |
session_delete |
| Sessions still up, with GPU totals | launcher_monitor (optional project) |
app is a path, id, or name. Built-ins include Terminal and Desktop. A container that is only a flow stage is refused.
launcher_add fills cores, memory, and GPU count from the instance-type catalog, the same way Add App does. A launcher cannot be saved without a project. --session-identity is system-admin only and is not an MCP field. See Session identity.
A session runs as the person who launched it. Only a shared desktop runs as the project user.
time accepts 30m, 2h, 90s, 1d, or 01:00:00. A value above the project maximum is refused. Extend cannot push the total past that maximum. At the maximum the message is that the max is reached and you should save your work. A batch job has no extend. eureka session launch LAUNCHER --time 30m stores 1800 seconds. eureka session status shows 30:00 before the clock starts, and counts down after the session is running.
launcher_monitor takes an optional project. With no project, an admin call lists every session and is slow. Pass a project when you want one project. A caller who is not an admin must pass a project.
Pause stops the VM and keeps the disk. Resume starts that VM on the kept disk. Delete ends the session and removes the VM and the disk, the same as Delete on the card. The command used to be named stop. The name is delete / session_delete.
Who can call them:
- Add a launcher: project Owner or Editor, or a system admin.
- Launch: any member of the launcher’s project, or a system admin.
- Pause, resume, delete, and extend: the session owner, the project Owner, or a system admin.
- Pause and resume also follow the environment switch that hides those buttons. See Apps.
session_launch, session_pause, and session_resume return as soon as the request is accepted. They do not wait for the machine. eureka session wait ID waits.
Flows, in the same server
Section titled “Flows, in the same server”list_flows, show_flow, export_flow, save_flow, submit_flow, delete_flow, flow_status, flow_monitor, and flow_run match eureka flow. Export includes the stage scripts. eureka flow import saves under a new name when that name is already on the project, and it says so. delete_flow refuses while a run is open unless stopRuns is true, which stops those runs and does not delete yet. See Flows.
Users and passwords
Section titled “Users and passwords”| What | CLI | MCP |
|---|---|---|
| Create a local user | eureka user add NAME [--password-file FILE] [--email EMAIL] [--first FIRST] [--last LAST] [--dir DIR] |
create_user (name, passwordFile; optional first, last, email, dir) |
| Change your password | eureka user chgpwd [--password-file FILE] [--current-password-file FILE] |
change_password (passwordFile, currentPasswordFile) |
| Reset another account | eureka user chgpwd NAME [--password-file FILE] |
change_password with user |
| Wait until the account can log in | eureka user wait NAME |
create_user is system admin only. It adds one Person with the local-password marker and sets the password through the existing admin reset. It does not grant system admin and it does not write LDAP itself. The existing person-provisioning event does that. The reply has ready false until eureka user wait reports the LDAP account, the home, and NSS. Creating the user is not that check.
Changing your own password requires the current password, including a non-interactive call. A system admin can reset a different account without it. That admin reset has to run on the control node. AFW refuses it on the login node. A new password must be at least 8 characters. Neither command accepts --password or --current-password. Those would put the secret in the process list. Use --password-file, --current-password-file, or the prompt, which does not echo.
MCP does not take the password as an argument. passwordFile and currentPasswordFile are absolute paths of mode 0600 files on the server where eureka mcp is running, owned by that Unix user, under that user’s home directory. The server rejects a symlink, a hard link, a path outside the home, the wrong owner, any other mode, and a file larger than 4096 bytes. It checks who is calling before it reads the file. A Grok vault reference id is not resolved. The file stays plaintext on that server until the caller deletes it.
approve_access_request with createUser still creates a passwordless federated account and does not take a password.
Admin tools
Section titled “Admin tools”Pause, resume, restart, and releasing held jobs are on Pause and resume the environment. Sign-in tools are on Sign-in. The environment sweep is on Environment overview.
system_notice_get, system_notice_set, and system_notice_clear are the banner on the Nodes page. eureka admin notice show, eureka admin notice set TEXT [--lead MINUTES], and eureka admin notice clear are the same banner.