MCP server for Megaplan — tasks, deals management via API v3.
MCP server for Megaplan project management — tasks, deals, projects, employees, comments via API v3. 8 tools + 2 MCP prompts. Token OR Password-grant auth. Stdio + Streamable HTTP transports. If you used v1.x, the v2.0.0 release introduces a few breaking changes: HTTP transport env var renamed: → . Removed separate codepath: v1 had a hand-rolled triggered by . v2 uses 's which auto-routes via…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
get_tasksNo description publishedThis tool published no description. Forge does not invent one.
create_taskNo description publishedThis tool published no description. Forge does not invent one.
get_dealsNo description publishedThis tool published no description. Forge does not invent one.
create_dealNo description publishedThis tool published no description. Forge does not invent one.
get_projectsNo description publishedThis tool published no description. Forge does not invent one.
get_employeesNo description publishedThis tool published no description. Forge does not invent one.
get_commentsNo description publishedThis tool published no description. Forge does not invent one.
create_commentNo description publishedThis tool published no description. Forge does not invent one.
0 of 8 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
MCP server for Megaplan project management — tasks, deals, projects, employees, comments via API v3. 8 tools + 2 MCP prompts. Token OR Password-grant auth. Stdio + Streamable HTTP transports. If you used v1.x, the v2.0.0 release introduces a few breaking changes: HTTP transport env var renamed: → . Removed separate codepath: v1 had a hand-rolled triggered by . v2 uses 's which auto-routes via flag OR env. Same CLI flag, different implementation (now with session management, endpoint, CORS,…
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.