Gantt MCP
Config file

Gantt charts in VS Code

mcp.json http entry, or a single terminal command

Add the server once and VS Code can schedule a whole project for you — dependencies, working calendars, resource levelling and critical path — then hand back a shareable chart plus PNG, SVG and CSV exports.

Set it up in 5 steps

Requires: GitHub Copilot access (the free plan is enough) and VS Code 1.102+. Copilot Business and Enterprise organisations need the "MCP servers in Copilot" policy enabled.

  1. Create `.vscode/mcp.json` in your project, or run `MCP: Open User Configuration` from the Command Palette to add it to your user profile (available across all workspaces).

    .vscode/mcp.json
    {
      "servers": {
        "gantt": {
          "type": "http",
          "url": "https://gantt.nare.li/api/mcp"
        }
      }
    }
  2. Save the file, then use the inline action (code lens) that appears above the "gantt" entry to start the server. Note that starting from the mcp.json editor skips the trust prompt; starting via `MCP: List Servers` shows it.

  3. VS Code opens a browser for the OAuth consent screen. It performs a Dynamic Client Registration handshake, so no clientId or token is needed — leave out the `oauth` and `headers` blocks entirely. Your authorization server must allow the redirect URIs `http://127.0.0.1:33418` and `https://vscode.dev/redirect`.

  4. Alternatively, skip the file and add the server to your user profile from a terminal in one command.

    bash
    code --add-mcp "{\"name\":\"gantt\",\"type\":\"http\",\"url\":\"https://gantt.nare.li/api/mcp\"}"
  5. Run `MCP: List Servers` to confirm gantt is running, then open Chat in agent mode and use the Configure Tools button in the chat input to toggle its tools on.

Leave out the oauth and headers blocks: VS Code performs dynamic client registration on its own.

Official documentation ↗

Once it is connected

Ask VS Code: “Plan a 6-week website rebuild for a team of four and give me the chart.”

Other clients