Bring Gantt Charts
to Claude Code
Learn how to connect TeamGantt to Claude Code and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the TeamGantt MCP Server?
Connect your TeamGantt account to any AI agent and simplify how you manage your project timelines, task assignments, and team resources through natural conversation.
What you can do
- Project Oversight — List all projects in your account and retrieve detailed metadata and configuration for specific Gantt charts.
- Task Management — Create, update, and delete tasks with full control over start/end dates and completion percentages.
- Timeline Coordination — Create dependencies between tasks to ensure your project logic remains sound and automated.
- Resource Tracking — List available resources (people and equipment) to optimize team allocation across projects.
- Milestone Planning — List and query major project goals (milestones) and sub-task checklists.
- Account Visibility — Fetch your user profile and verify account configurations directly from the agent.
How it works
1. Subscribe to this server
2. Enter your TeamGantt API Token (found in your account settings under API)
3. Start managing your timelines from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Project Managers — quickly check task progress and update project timelines via simple AI commands.
- Operations Teams — coordinate resource assignments and verify dependencies directly from the workspace.
- Engineering Leads — monitor milestones and update task completion percentages via the AI assistant.
Built-in capabilities (12)
Add task to project
Get user info
Get project info
List sub-tasks
Get task details
g. Task A must finish before Task B starts). Create Gantt link
List users and labels
List major goals
List tasks in project
List TeamGantt projects
Delete task
). Update task status/dates
Why Claude Code?
Claude Code registers TeamGantt as an MCP server in a single terminal command. Once connected, Claude Code discovers all 12 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where TeamGantt data drives decisions without human intervention.
- —
Single-command setup:
claude mcp addregisters the server instantly. no config files to edit or applications to restart - —
Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks
- —
Claude Code runs headlessly, enabling unattended batch processing using TeamGantt tools in cron jobs or deployment scripts
- —
Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features
TeamGantt in Claude Code
TeamGantt and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect TeamGantt to Claude Code through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for TeamGantt in Claude Code
The TeamGantt MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Code only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
TeamGantt for Claude Code
Every tool call from Claude Code to the TeamGantt MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I see all the tasks in a project via AI?
Yes! Use the list_project_tasks tool and provide the Project ID. Your agent will retrieve all tasks, milestones, and groups for that specific Gantt chart.
How do I update the progress of a task using the agent?
Use the update_task_fields action. Provide the Task ID and the percentComplete value (0-100) to update the task's status instantly.
Is it possible to link two tasks with a dependency via AI?
Absolutely. Use the link_tasks_dependency tool. Provide the ID of the predecessor and the successor tasks to create a Gantt link between them.
How do I add an MCP server to Claude Code?
Run claude mcp add --transport http "" in your terminal. Claude Code registers the server and discovers all tools immediately.
Can Claude Code run MCP tools in headless mode?
Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.
How do I list all connected MCP servers?
Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.
Command not found: claude
Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code
Connection timeout
Check your internet connection and verify the Edge URL is reachable
