elma365-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ELMA365_TOKEN | Yes | Bearer-токен для ELMA365 API | |
| ELMA365_DOMAIN | Yes | Домен ELMA365 (например, mycompany для mycompany.elma365.ru, или полный домен mycompany.elma365.ru) |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_app_itemsC | Получить список элементов приложения ELMA365 по namespace и code. |
| create_itemC | Создать новый элемент в приложении ELMA365. |
| get_tasksC | Получить список BPM-задач ELMA365. |
| get_processesC | Получить список бизнес-процессов ELMA365. |
| start_processC | Запустить бизнес-процесс ELMA365 по коду. |
| get_usersB | Получить список пользователей ELMA365. |
| get_user_by_idC | Получить пользователя ELMA365 по ID. |
| get_commentsB | Получить комментарии к элементу приложения ELMA365. |
| add_commentC | Добавить комментарий к элементу приложения ELMA365. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a distinct resource or action: items, comments, processes, tasks, and users are clearly separated. The pairs like get_users/get_user_by_id and get_comments/add_comment are easily distinguishable as list vs. specific, causing no ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_item, get_tasks, start_process). The verbs are appropriate and the naming is predictable across the entire set.
With 9 tools covering common operations on items, comments, processes, tasks, and users, the count is well-scoped. Each tool serves a distinct purpose without unnecessary duplication or bloat.
The tool surface has significant gaps: items lack get single, update, and delete; comments lack delete; processes lack stop; tasks lack update. These missing operations limit the ability to perform full CRUD or lifecycle management for the domain.