Lalaleap MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LALALEAP_EMAIL | No | Login email (required if not using API token) | |
| LALALEAP_API_URL | Yes | API base URL (required) | |
| LALALEAP_PASSWORD | No | Login password (required if not using API token) | |
| LALALEAP_READONLY | No | Set to '1' to enable read-only mode | |
| LALALEAP_API_TOKEN | No | API token for authentication (alternative to email/password) | |
| LALALEAP_UNSAFE_SSL | No | Set to '1' to skip SSL verification | |
| LALALEAP_ALLOWED_PROJECTS | No | Comma-separated list of project pnos that are allowed to be written | |
| LALALEAP_WRITE_RATE_LIMIT | No | Maximum write operations per minute (default 10) | 10 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsB | 列出使用者可存取的專案清單 |
| get_project_detailC | 取得專案詳細資訊 |
| create_projectA | 建立新專案（寫入操作，受頻率限制保護） |
| create_requirementA | 在指定專案中建立一筆需求（寫入操作，受白名單與頻率限制保護） |
| list_requirementsB | 查詢指定專案的需求清單 |
| get_requirement_detailB | 取得單筆需求的完整資訊 |
| update_requirementB | 更新需求欄位（寫入操作，受白名單與頻率限制保護） |
| create_bugA | 在指定專案中建立一筆缺陷（寫入操作，受白名單與頻率限制保護） |
| list_bugsC | 查詢指定專案的缺陷清單 |
| update_bugB | 更新缺陷欄位（寫入操作，受白名單與頻率限制保護） |
| create_todoB | 在指定專案中建立待辦項目（寫入操作，受白名單與頻率限制保護） |
| list_todosC | 查詢專案的待辦看板（含欄位與項目） |
| list_sprintsC | 查詢專案的迭代清單 |
| search_tagsC | 搜尋專案標籤 |
| list_project_membersB | 查詢專案成員 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| projects | 使用者的專案清單 |
TDQS
Scored across 15 tools
Each tool targets a distinct resource (project, requirement, bug, todo, sprint, member, tag) with specific actions (create, get, list, update). No overlap in responsibilities.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., create_project, list_requirements, update_bug). No mixed conventions.
15 tools is well-scoped for a project management server. It covers core entities and common operations without being excessive or too sparse.
Covers create, list, get, and update for requirements, bugs, and todos, but lacks delete operations entirely. Also missing sprint creation/update and member management (only list). These are notable gaps.