Megaplan MCP server

megaplan-mcp

An MCP server for the Megaplan v3 API: tasks, deals, projects and employees through an agent, plus ready-made skills for daily tasks and a deal wizard

MCP serverRussian stack

theyahia/megaplan-mcpAuthor:theYahia

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/megaplan-mcp

Detects the agents on your machine, checks the risk and pins the version.

Other ways to install

This entry is high risk, so there is no one-click install. Review the code and add the config by hand.

Run in a terminal

claude mcp add --transport stdio --env 'MEGAPLAN_DOMAIN=<MEGAPLAN_DOMAIN value>' megaplan -- npx -y @theyahia/megaplan-mcp

Or add to the file .mcp.json, in the project

{
  "mcpServers": {
    "megaplan": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/megaplan-mcp"
      ],
      "env": {
        "MEGAPLAN_DOMAIN": "<MEGAPLAN_DOMAIN value>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

MEGAPLAN_DOMAINrequired
MEGAPLAN_TOKENsecret, optional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.cursor/mcp.json, for all projects

{
  "mcpServers": {
    "megaplan": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/megaplan-mcp"
      ],
      "env": {
        "MEGAPLAN_DOMAIN": "<MEGAPLAN_DOMAIN value>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.

Keys and settings

MEGAPLAN_DOMAINrequired
MEGAPLAN_TOKENsecret, optional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Run in a terminal

code --add-mcp '{"name":"megaplan","type":"stdio","command":"npx","args":["-y","@theyahia/megaplan-mcp"],"env":{"MEGAPLAN_DOMAIN":"<MEGAPLAN_DOMAIN value>"}}'

Or add to the file .vscode/mcp.json, in the project

{
  "servers": {
    "megaplan": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/megaplan-mcp"
      ],
      "env": {
        "MEGAPLAN_DOMAIN": "<MEGAPLAN_DOMAIN value>"
      }
    }
  }
}

If the file already exists, add the server inside the servers key.

Keys and settings

MEGAPLAN_DOMAINrequired
MEGAPLAN_TOKENsecret, optional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Run in a terminal

codex mcp add megaplan --env 'MEGAPLAN_DOMAIN=<MEGAPLAN_DOMAIN value>' -- npx -y @theyahia/megaplan-mcp

Or add to the file ~/.codex/config.toml, for all projects

[mcp_servers.megaplan]
command = "npx"
args = ["-y", "@theyahia/megaplan-mcp"]
env = { MEGAPLAN_DOMAIN = "<MEGAPLAN_DOMAIN value>" }

If the file already exists, append the block to the end.

Keys and settings

MEGAPLAN_DOMAINrequired
MEGAPLAN_TOKENsecret, optional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.gemini/settings.json, for all projects

{
  "mcpServers": {
    "megaplan": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/megaplan-mcp"
      ],
      "env": {
        "MEGAPLAN_DOMAIN": "<MEGAPLAN_DOMAIN value>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

MEGAPLAN_DOMAINrequired
MEGAPLAN_TOKENsecret, optional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/devin/mcp_config.json, for all projects

{
  "mcpServers": {
    "megaplan": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/megaplan-mcp"
      ],
      "env": {
        "MEGAPLAN_DOMAIN": "<MEGAPLAN_DOMAIN value>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.

Keys and settings

MEGAPLAN_DOMAINrequired
MEGAPLAN_TOKENsecret, optional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Formerly Windsurf.

Add to the file cline_mcp_settings.json, for all projects

{
  "mcpServers": {
    "megaplan": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/megaplan-mcp"
      ],
      "env": {
        "MEGAPLAN_DOMAIN": "<MEGAPLAN_DOMAIN value>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.

Keys and settings

MEGAPLAN_DOMAINrequired
MEGAPLAN_TOKENsecret, optional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file .roo/mcp.json, in the project

{
  "mcpServers": {
    "megaplan": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/megaplan-mcp"
      ],
      "env": {
        "MEGAPLAN_DOMAIN": "<MEGAPLAN_DOMAIN value>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

MEGAPLAN_DOMAINrequired
MEGAPLAN_TOKENsecret, optional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

A fork of Roo Code, same .roo folders.

Add to the file opencode.json, in the project

{
  "mcp": {
    "megaplan": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@theyahia/megaplan-mcp"
      ],
      "environment": {
        "MEGAPLAN_DOMAIN": "<MEGAPLAN_DOMAIN value>"
      }
    }
  }
}

If the file already exists, add the server inside the mcp key.

Keys and settings

MEGAPLAN_DOMAINrequired
MEGAPLAN_TOKENsecret, optional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/zed/settings.json, for all projects

{
  "context_servers": {
    "megaplan": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/megaplan-mcp"
      ],
      "env": {
        "MEGAPLAN_DOMAIN": "<MEGAPLAN_DOMAIN value>"
      }
    }
  }
}

If the file already exists, add the server inside the context_servers key.

Keys and settings

MEGAPLAN_DOMAINrequired
MEGAPLAN_TOKENsecret, optional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file .codeassistant/mcp.json, in the project

{
  "mcpServers": {
    "megaplan": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/megaplan-mcp"
      ],
      "env": {
        "MEGAPLAN_DOMAIN": "<MEGAPLAN_DOMAIN value>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

MEGAPLAN_DOMAINrequired
MEGAPLAN_TOKENsecret, optional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

You will need: Node.js

Checked against the repository on Sep 25, 2026, commit 9cbf2f5.

Text for your agent

Generate an access token in Megaplan (Settings → Integrations → API) and connect the server via npx -y @theyahia/megaplan-mcp with the MEGAPLAN_DOMAIN and MEGAPLAN_TOKEN variables in your MCP client config.

Other ways from the author

{
  "mcpServers": {
    "megaplan": {
      "command": "npx",
      "args": ["-y", "@theyahia/megaplan-mcp"],
      "env": {
        "MEGAPLAN_DOMAIN": "yourcompany",
        "MEGAPLAN_TOKEN": "your-access-token"
      }
    }
  }
}

The access-token config from the README.

This is third-party code. Review the repository files before installing.

What it does

The server gives eight tools over the Megaplan v3 API: listing tasks with status and assignee filters, creating a task with a deadline, listing and creating deals with a pipeline, amount and contact, listing projects, listing employees with search and department filters, and reading or adding comments to a task, deal or project. It also ships two ready MCP prompts: "my tasks for today" pulls active tasks by urgency, and a deal-creation wizard walks through creating a deal step by step. Authorization works two ways: an access token from the integration settings, or a Megaplan account login and password. Besides stdio, the server can run as Streamable HTTP for remote deployment via the --http flag.

Who it is for. For Megaplan teams who want to create tasks and manage deals from a chat with an agent without opening the interface.

Good fit when

You want to quickly create a task or deal with an amount and contact in words
You want a daily list of active tasks sorted by urgency
You need a remote HTTP server instead of local stdio, for example for a cloud deployment

Not a fit when

You need to delete tasks or deals, or handle Megaplan documents, files or reports: the tool set is limited to eight tools
You prefer storing only a token, not a password: login and password is the fallback, less secure method

Example request

Create a 300,000 rouble deal for this contact in Megaplan

Limitations

Only eight tools: no deletion, documents, files or reports. One of two login methods is required: either MEGAPLAN_TOKEN, or the MEGAPLAN_LOGIN and MEGAPLAN_PASSWORD pair, and choosing the password method passes credentials to the server directly. Single author, part of the personal WWmcp series.

How to disable. Remove the megaplan server with claude mcp remove megaplan, or delete it from claude_desktop_config.json.

MCP

Transport: stdio, http
Authentication: API key

Environment variables
Environment variables
MEGAPLAN_DOMAIN required	Megaplan subdomain, e.g. yourcompany
MEGAPLAN_TOKEN secret	Access token from Settings → Integrations → API, one of two options along with login and password
MEGAPLAN_LOGIN	Login e-mail if no token is used
MEGAPLAN_PASSWORD secret	Password if no token is used

Security check

Creates deals and tasks visible to the whole team in Megaplan
Logging in with login and password passes account credentials to the server

README in short

The README lists the eight tools and two skills in tables, shows two authorization methods (token, or login with password), a Claude Desktop config for both, running in Streamable HTTP mode via the --http flag with the port set by the PORT variable, and development commands (build, tests, dev mode).

FAQ

Can I connect without a token?

Yes, MEGAPLAN_LOGIN and MEGAPLAN_PASSWORD for a Megaplan account can be set instead of MEGAPLAN_TOKEN.

Are there ready scenarios, not just individual tools?

Yes, two skills: my-tasks-today for a daily task summary and create-deal-wizard for step-by-step deal creation.

Salesforce DX MCP Server

Official

Salesforce's official DX MCP server: work with orgs, metadata, data, users and Apex tests from your agent

MCP serverHigh risk483

Yandex Kit skills for store management

kit-skills

Official

Yandex's official skill set: catalog, prices, stock, orders, storefront and a weekly checkup for a Yandex Kit store, through Claude Code or Codex

PluginHigh riskRussian stackNo VPN needed28

YouGile MCP by Indalo

YouGile MCP

Editors’ pick

Full 65-operation YouGile API coverage with configurable permissions, write confirmation and a shared company rate limit

MCP serverHigh riskRussian stackNo VPN needed

Bitrix24 portal MCP server

MCP-сервер портала Битрикс24

Official

Bitrix24's official per-portal MCP: an external agent uses OAuth or a token to read and change tasks, deals, meetings and mail

MCP serverHigh riskRussian stackNo VPN needed

Install

What it does

Good fit when

Not a fit when

Example request

Limitations

MCP

Security check

README in short

FAQ

Related

Salesforce DX MCP Server

Yandex Kit skills for store management

YouGile MCP by Indalo

Bitrix24 portal MCP server