TeamGantt MCP Server for VS Code CopilotGive VS Code Copilot instant access to 12 tools to Create New Task, Get Account Profile, Get Project Details, and more
GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.
Ask AI about this App Connector for VS Code Copilot
The TeamGantt app connector for VS Code Copilot is a standout in the Productivity category — giving your AI agent 12 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install TeamGantt and 3,400+ MCP Servers from a single visual interface.




{
"mcpServers": {
"teamgantt": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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
About 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.
GitHub Copilot Agent mode brings TeamGantt data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 12 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
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.
The TeamGantt MCP Server exposes 12 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
All 12 TeamGantt tools available for VS Code Copilot
When VS Code Copilot connects to TeamGantt through Vinkius, your AI agent gets direct access to every tool listed below — spanning gantt-charts, project-planning, task-management, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.
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
Connect TeamGantt to VS Code Copilot via MCP
Follow these steps to wire TeamGantt into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Create MCP config
.vscode/mcp.json file in your project rootAdd the server config
Enable Agent mode
Start using TeamGantt
Why Use VS Code Copilot with the TeamGantt MCP Server
GitHub Copilot for Visual Studio Code provides unique advantages when paired with TeamGantt through the Model Context Protocol.
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
TeamGantt + VS Code Copilot Use Cases
Practical scenarios where VS Code Copilot combined with the TeamGantt MCP Server delivers measurable value.
Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step
DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review
Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses
Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples
Example Prompts for TeamGantt in VS Code Copilot
Ready-to-use prompts you can give your VS Code Copilot agent to start working with TeamGantt immediately.
"List all active projects in my TeamGantt account."
"Show me the tasks for 'Website Launch Q4' (ID: 10293)."
"Mark task '88231' as 100% complete."
Troubleshooting TeamGantt MCP Server with VS Code Copilot
Common issues when connecting TeamGantt to VS Code Copilot through the Vinkius, and how to resolve them.
MCP tools not available
TeamGantt + VS Code Copilot FAQ
Common questions about integrating TeamGantt MCP Server with VS Code Copilot.
Which VS Code version supports MCP?
How do I switch to Agent mode?
Can I restrict which MCP tools Copilot can access?
Does MCP work in VS Code Remote or Codespaces?
.vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.