Bring Gantt Charts
to Claude Desktop
Learn how to connect TeamGantt to Claude Desktop 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 Desktop?
Claude Desktop is the definitive way to connect TeamGantt to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 12 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
TeamGantt in Claude Desktop
TeamGantt and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect TeamGantt to Claude Desktop 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 Desktop
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 Desktop 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 Desktop
Every tool call from Claude Desktop 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 does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.
