Elnora Projects

Manage projects on the Elnora AI Platform. Projects are containers for tasks, files, and folders.

Tool Access

Elnora is available via two methods. Use whichever is configured.

Option A — CLI via Bash (preferred)

Run commands via your Bash/Shell tool as elnora <group> <action> .... Verify with elnora --version. CLI uses ~5× fewer tokens than MCP.

Option B — MCP tools (when CLI isn't installed)

Look for tools prefixed mcp__elnora__ in your available tools. Call them with structured parameters (camelCase — e.g. projectId, not project-id). See the "MCP Tool Names" table below for the mapping.

If neither is available, tell the user to install one:

• CLI: curl -fsSL https://cli.elnora.ai/install.sh | bash (macOS/Linux)

or irm https://cli.elnora.ai/install.ps1 | iex (Windows)

• MCP: claude mcp add elnora --transport http --scope user https://mcp.elnora.ai/mcp

then /mcp to authenticate.

Never fabricate tool names. Valid commands are in the Commands section; their MCP equivalents are in the MCP Tool Names table.

Invocation

CLI="elnora"

Commands

List Projects

$CLI --compact projects list
$CLI --compact projects list --page 2 --page-size 50
$CLI --compact --fields "id,name" projects list

Response:

{"items":[{"id":"<UUID>","name":"...","description":"...","isDefault":false,"isArchived":false,"memberCount":1,"myRole":"owner","createdAt":"..."}],"page":1,"totalCount":N,"hasNextPage":false}

Get Project

$CLI --compact projects get <PROJECT_ID>

Returns project detail with members array.

Create Project

$CLI --compact projects create --name "Protocol Lab" --description "PCR protocols" --icon "lab"

Update Project

$CLI --compact projects update <PROJECT_ID> --name "New Name"
$CLI --compact projects update <PROJECT_ID> --description "Updated description"

Must provide at least one of --name, --description, or --icon.

Archive Project

$CLI --compact projects archive <PROJECT_ID>
# -> {"archived":true,"projectId":"<UUID>"}

Destructive — confirm with user before running.

List Members

$CLI --compact projects members <PROJECT_ID>

Add Member

$CLI --compact projects add-member <PROJECT_ID> <USER_ID> --role Member

Both <PROJECT_ID> and <USER_ID> are positional (projectId and userId). --role defaults to "Member".

Update Member Role

$CLI --compact projects update-role <PROJECT_ID> <USER_ID> --role Admin

Both positional. --role is required.

Remove Member

$CLI --compact projects remove-member <PROJECT_ID> <USER_ID>
# -> {"removed":true}

Both positional. Destructive — confirm with user before running.

Leave Project

$CLI --compact projects leave <PROJECT_ID>

Removes the current user from the project.

Choosing a Project

Many commands require a project ID. Resolve it once per session, then reuse.

$CLI --compact --fields "id,name" projects list

Decision tree:

1. One project → use it automatically, don't ask.
2. 2–5 projects → show the list, ask the user to pick by name or number. Remember the choice.
3. 6+ projects → ask the user to name or describe their project. Match by name. Don't dump the full list.
4. Zero projects → tell the user to create one: $CLI projects create --name "My Project".

Never re-list projects for every command. Cache the project ID after the first lookup. If the user says "switch to project X", re-list then.

MCP Tool Names

Agent Recipes

Full project setup with members:

PROJECT=$($CLI --compact projects create --name "New Lab" | jq -r '.id')
$CLI --compact projects add-member "$PROJECT" <USER_ID> --role Member