megaplan-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP port for --http mode (default: 3000) | 3000 |
| MEGAPLAN_LOGIN | No | Login email (if no token) | |
| MEGAPLAN_TOKEN | No | Bearer access token | |
| MEGAPLAN_DOMAIN | Yes | Megaplan subdomain (e.g. yourcompany) | |
| MEGAPLAN_PASSWORD | No | Password (if no token) |
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
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_tasksB | List tasks from Megaplan with filters by status, responsible user, and search. |
| create_taskB | Create a new task in Megaplan with name, description, responsible user, and deadline. |
| get_dealsB | List deals from Megaplan with filters by status, responsible user, and search. |
| create_dealB | Create a new deal in Megaplan with name, pipeline, responsible user, and amount. |
| get_projectsA | List projects from Megaplan with filters by status and search. |
| get_employeesB | List employees from Megaplan with search and department filter. |
| get_commentsA | List comments for a task, deal, or project in Megaplan. |
| create_commentA | Add a comment to a task, deal, or project in Megaplan. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| my-tasks-today | Мои задачи на сегодня — shows your tasks due today or overdue |
| create-deal-wizard | Создай сделку — guided deal creation wizard |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct entity and action (create vs get). There is no ambiguity between tasks, deals, projects, comments, or employees.
All tools follow a consistent verb_noun pattern (create_* or get_*) with underscores, making them predictable and easy to remember.
With 8 tools, the server is well-scoped for a basic project management API, covering core create and read operations across key entities.
Significant gaps exist: there are no update or delete tools for any entity, and no create_employee. This leaves agents unable to modify or remove items, which is a major limitation.