Task Manager MCP Server

Node.js MCP server using LLMs (Gemini/OpenRouter) for AI-assisted task planning, breakdown, and code review. Designed for Cursor integration.

Local serverstdioGo

What is the Task Manager MCP server?

Node.js MCP server using LLMs (Gemini/OpenRouter) for AI-assisted task planning, breakdown, and code review. Designed for Cursor integration. That is what the task manager mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

This is an MCP server built to integrate with AI code editors like Cursor. The main goal here is to maximize Cursor's agentic capabilities and Gemini 2.5's excellent architecting capabilities while working around Cursor's extremely limited context window. This was inspired largely by Roo Code's Boomerang mode, but I found it extremely expensive as the only model that works with it's apply bot is Claude 3.7 Sonnet. With this server, you get the best of both worlds: unlimited context window and unlimited usage for the price of Cursor's $20/month subscription.

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

What it needs from you

Configuration is passed through the environment: OPENROUTER_API_KEY, OPENROUTER_MODEL, FALLBACK_OPENROUTER_MODEL, UI_PORT, WS_PORT, GEMINI_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • Node.js - npm - Git

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by jhawkins11; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

How to install the Task Manager MCP server

{
  "mcpServers": {
    "task-manager-mcp": {
      "command": "node",
      "args": ["/full/path/to/your/task-manager-mcp/dist/server.js"],
      "env": {
        "OPENROUTER_API_KEY": "sk-or-v1-xxxxxxxxxxxxxxxxxxxx"
        //   optional: my recommended model for MCP is Gemini 2.5 Pro Free which is already set by default
        //   "OPENROUTER_MODEL": "google/gemini-2.5-flash-preview:thinking",
        //   also optional
        //   "FALLBACK_OPENROUTER_MODEL": "google/gemini-2.5-flash-preview:thinking",
        //   optional: the default port for the UI is 4999 if not set
        //   "UI_PORT": "4999",
        //   optional: the default port for the WebSocket server is 4999 if not set
        //   "WS_PORT": "4999"
        // Add GEMINI_API_KEY here instead if using Google directly
        // Add any other necessary env vars here
      }
    }
    // Add other MCP servers here if you have them
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Node.js - npm - Git
VariableDescriptionRequired
OPENROUTER_API_KEYCredential the server authenticates with.Yes
OPENROUTER_MODELConfiguration value read at startup.Optional
FALLBACK_OPENROUTER_MODELConfiguration value read at startup.Optional
UI_PORTConfiguration value read at startup.Optional
WS_PORTConfiguration value read at startup.Optional
GEMINI_API_KEYCredential the server authenticates with.Yes

Frequently asked questions

It lets Cursor (or similar AI editors) plan and execute complex features one task at a time, overcoming context‑window limits by using Gemini 2.5’s 1‑million‑token context and a structured workflow.