list_user_lists

MCP tool from Elemctl by keyfire

user lists; name filters by a substring of the presentation

How to use it

list_user_lists is exposed by the Elemctl MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), and the list_user_lists tool becomes available to the model automatically. See the full listing for setup details and every tool this server provides.

Install Elemctl

$claude mcp add elemctl -- elemctl mcp

FULL ELEMCTL LISTING

Other tools in Elemctl (23)

apply_build

apply an uploaded build to the application by its id

build_assembly

build a .xasm/.xlib archive from the sources locally (does not talk to the platform)

configure_user_list

self-registration and password sign-in; without the flags it only reports the current state

create_app

create an application; with only a projectid the source is the project's latest build. The answer carries sign-in – the way in

debug_adapter

the path to the platform debug adapter from a plugin; a missing plugin is an answer (found: false), not an error (local)

debug_info

debug-session data: debug-token and debug-address (debugging must be enabled on the server)

delete_app

delete the application. IRREVERSIBLE: the data is lost, and a recreated application gets a different URL

deploy

the whole cycle from sources with the honest apply verification; the verdict is ok, the details are problems and log

ensure_app

create an application by name only if it does not exist yet; an existing one is not recreated (created: false)

find_app

find an application by its exact name: the id and a found flag; deleted ones are skipped unless includedeleted is set

get_app

application card: status, uri, the actual project version

inspect_assembly

parse a built archive: manifest, project properties, subsystems and global types with qualified names (local)

list_app_tasks

tasks of the applications; appid is an optional filter

list_apps

list of applications; name filters by a substring of the name on the client, brief (the default) keeps id, name, status, uri and the applied version

list_branches

list of development-environment branches; the projectid and name filters are optional

list_builds

list of a project's builds, newest first; limit (default 10, 0 – all), brief (the default) keeps id, versions, date, branch and commit

list_projects

list of projects; name filters by a substring of the name on the client, the deleted ones are hidden unless includedeleted is set; brief (the default) – id, name, project kind, space, application count, deletion flag

list_spaces

list of spaces

merge_branch

accept the changes of a development-environment branch

probe

check the compilation with the server compiler WITHOUT touching the working application; errors with file, line and column, cleans up after itself

start_app

start the application

stop_app

stop the application

verify_deploy

verify the apply actually took effect: failed tasks, the applied build, the availability of the uri