Loopgantt MCP

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

• 연결 방식: 컴퓨터 또는 클라우드
• 전송 방식: stdio, Streamable HTTP
• 카테고리: 디자인, 이미지 및 오디오
• 입력해야 할 값: LOOPGANTT_API_KEY

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

필요한 것

• 클라우드에서 실행설치할 것 없음. 인터넷으로 연결돼요
• npmNode.js 설치(npx 명령어용)

어떤 앱을 쓰세요?

https://loopgantt.com/api/mcp

{
  "mcpServers": {
    "loopgantt": {
      "command": "npx",
      "args": [
        "-y",
        "@loopgantt/mcp-server"
      ],
      "env": {
        "LOOPGANTT_API_KEY": "your-value"
      }
    }
  }
}

claude mcp add --transport http loopgantt https://loopgantt.com/api/mcp

claude mcp add loopgantt --env LOOPGANTT_API_KEY=your-value -- npx -y @loopgantt/mcp-server

{
  "mcpServers": {
    "loopgantt": {
      "url": "https://loopgantt.com/api/mcp"
    }
  }
}

{
  "mcpServers": {
    "loopgantt": {
      "command": "npx",
      "args": [
        "-y",
        "@loopgantt/mcp-server"
      ],
      "env": {
        "LOOPGANTT_API_KEY": "your-value"
      }
    }
  }
}

{
  "servers": {
    "loopgantt": {
      "type": "http",
      "url": "https://loopgantt.com/api/mcp"
    }
  }
}

{
  "servers": {
    "loopgantt": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@loopgantt/mcp-server"
      ],
      "env": {
        "LOOPGANTT_API_KEY": "your-value"
      }
    }
  }
}

https://loopgantt.com/api/mcp

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

직접 입력할 값

• LOOPGANTT_API_KEY 비밀 env
  Optional. Enables the account tools create_project / list_projects (https://loopgantt.com/settings/api-keys).

이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.

할 수 있는 일

도구 이름과 설명은 서버가 2026년 11월 9일에 알려 준 그대로예요. 우리가 아니라 제작자가 쓴 글이고, 일반 텍스트로만 보여 드려요.

• create_gantt

  Create a Gantt chart from a task list — no account or API key needed. YOU author the plan: list the tasks in execution order with realistic working-day durations and dependencies (0-based positions of earlier tasks; use { task, type, lag } for start-to-start/finish-to-finish link

• schedule_project

  Compute a schedule without storing anything: dates, critical path, float and project end for a task list (same input shape as create_gantt; name optional). Use it to answer "what is the critical path?", "when would this finish?", "how much slack does X have?". Use create_gantt wh

• list_templates

  List LoopGantt's industry project templates with task counts and typical durations. Pick one, fetch it with get_template, adapt it, then create_gantt.

• get_template

  Get one industry template by slug: its task list with durations, ready to adapt and pass to create_gantt.

• create_project

  Create a project in the connected LoopGantt ACCOUNT (requires a LoopGantt API key). For a keyless chart use create_gantt instead. Pass workflow: "agent_board" for a board a team of agents works on - stages todo, in_progress, blocked, waiting_approval, done (done is the finished s

• list_projects

  List the projects in the connected LoopGantt account (requires a LoopGantt API key), with each project's workflow stages: use one of those stage ids as a task's status.

• list_tasks

  List tasks in the connected LoopGantt ACCOUNT (requires a LoopGantt API key), across every project the account can reach, most recently changed first. Use it to answer "what am I working on", to find a task before changing it, or to catch up on what moved: pass updatedSince (ISO

• update_task

  Change one task in the connected LoopGantt ACCOUNT (requires a LoopGantt API key). Pass the taskId from list_tasks and only the fields to change. To mark a task done use complete_task — LoopGantt couples status and progress, and complete_task says exactly that. Set agentLabel to

• complete_task

  Mark one task done in the connected LoopGantt ACCOUNT (requires a LoopGantt API key). LoopGantt treats done as status AND 100 % together, so this sets both through the same rule the app uses - never set progress to 100 by hand with update_task and hope the status follows.

• create_task

  Add one task to an existing project in the connected LoopGantt ACCOUNT (requires a LoopGantt API key). Put it under a phase with parentId, make it wait for other tasks with dependencies, and hand it to a person with assigneeId or to a bot with agentLabel (e.g. "qa-bot"). Returns

• delete_task

  Delete one task in the connected LoopGantt ACCOUNT (requires a LoopGantt API key) - and every task under it when it is a phase. DESTRUCTIVE: ask the user before calling, and pass confirm: true only after they agreed; without it nothing is deleted. The task goes to the project tra

• add_comment

  Leave a comment on a task in the connected LoopGantt ACCOUNT (requires a LoopGantt API key) — notes, handoffs between agents, questions for a person. It shows in the task timeline, notifies the task watchers and @-mentioned people, and fires the comment.posted webhook.

• list_comments

  Read the comments on one task in the connected LoopGantt ACCOUNT (requires a LoopGantt API key), newest first — to pick up a handoff or see what a person decided.

• get_changes

  What changed in the connected LoopGantt ACCOUNT (requires a LoopGantt API key) since an instant: tasks created, tasks now done and tasks otherwise updated. Built for agents that poll: the first time pass since (e.g. when you last looked); after that pass back BOTH the since and t

• list_overdue

  Open tasks whose scheduled end has passed, in the connected LoopGantt ACCOUNT (requires a LoopGantt API key), most overdue first.

• list_due_soon

  Open tasks scheduled to end within the next N days (today included), in the connected LoopGantt ACCOUNT (requires a LoopGantt API key), earliest end first.

• create_meeting

  Book a meeting in the connected LoopGantt ACCOUNT (requires a LoopGantt API key); the key owner is the organizer. Every invitee gets a calendar invitation (.ics, works with Apple, Google, Outlook and any other calendar); members with Google or Outlook sync get it straight in that

• list_meetings

  Meetings in the connected LoopGantt ACCOUNT (requires a LoopGantt API key): the key owner's meetings in a window, a project's meetings in a window, or the upcoming meetings about one task.

• link_external

  Attach a link to a task in the connected LoopGantt ACCOUNT (requires a LoopGantt API key): the GitHub PR, Jira or Linear issue, Google Doc, Figma file or Slack thread the work lives in, so people and other agents can follow it and find the task again with find_by_link. A GitHub P

• list_links

  The links attached to one task in the connected LoopGantt ACCOUNT (requires a LoopGantt API key): PRs, issues, docs and threads in other apps.

• find_by_link

  Which tasks in the connected LoopGantt ACCOUNT (requires a LoopGantt API key) carry this link — e.g. the task a Jira issue, PR or doc belongs to. Searches only projects the key owner can see.

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 10일 점검

• ! 주의

  제작자와 저장소 일치

  레지스트리에 소스 저장소가 없어서, 게시자(loopgantt.com)와 코드를 맞춰 볼 수 없어요

• … 아직 점검 안 함

  계속 관리되고 있음

  아직 GitHub에서 이 저장소를 읽어 오지 않았어요

• … 아직 점검 안 함

  라이선스 있음

  아직 GitHub에서 이 저장소를 읽어 오지 않았어요

• ✓ 통과

  엔드포인트 응답

  324ms 만에 응답(HTTP 200)

• – 해당 없음

  OAuth로 로그인

  로그인 필요 없음

• ✓ 통과

  도구 설명에 숨겨진 지시 없음

  도구 설명 21개를 읽었고, AI에게 보내는 숨겨진 지시는 없었어요

디자인, 이미지 및 오디오 카테고리의 다른 서버와 비교i

• 이 카테고리의 다른 서버 2873개 중 0%보다 스타가 많아요
• 이 카테고리의 다른 서버 2873개 중 26%보다 최근에 레지스트리에 공개됐어요
• 기본 점검 결과가 이 카테고리의 다른 서버 2873개 중 45%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:↓ 주간 다운로드i★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

제작자의 README

저장소에서 README를 찾지 못했어요