@theyahia/getcourse-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTP_PORT | No | Port for HTTP transport (e.g. 3000) | |
| GETCOURSE_DOMAIN | Yes | Account domain (e.g. myschool.getcourse.ru) | |
| GETCOURSE_API_KEY | Yes | API secret key from account settings |
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_usersC | Получение списка пользователей GetCourse. |
| create_userB | Создание или обновление пользователя в GetCourse. |
| get_dealsC | Получение списка заказов (сделок) GetCourse. |
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 3 tools
Each tool targets a distinct resource and action: getting users, creating/updating users, and getting deals. There is no overlap or ambiguity between the tools.
All tools follow a consistent verb_noun pattern with get_ or create_ prefixes (get_users, create_user, get_deals). Naming is predictable and uniform.
With exactly 3 tools, the count falls within the well-scoped 3-15 range. Each tool serves a clear core function for GetCourse integration without unnecessary bloat.
The tool surface covers listing users, upserting users, and listing deals, but notable operations are missing: no delete for users and no create/update/delete for deals. This creates partial CRUD coverage with gaps.