Bring Agile Methodology
to VS Code Copilot
Learn how to connect VivifyScrum to VS Code Copilot 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 VivifyScrum MCP Server?
Connect your VivifyScrum account to any AI agent and simplify how you manage your Scrum and Kanban workflows through natural conversation.
What you can do
- Board Management — List all boards and organizations, and retrieve detailed configuration metadata for specific project spaces.
- Task Control — Create, list, and update items (tasks and stories) directly on your agile boards.
- Sprint Planning — List sprints for a board to track progress and plan future development cycles.
- Team Coordination — Query team lists and organization members to manage access and visibility.
- Operational Tracking — Monitor worklogs for time tracking and list configured webhooks for event monitoring.
How it works
1. Subscribe to this server
2. Enter your VivifyScrum API Token (found in your account profile settings)
3. Start managing your agile projects from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Project Managers & Scrum Masters — quickly retrieve board items and sprint statuses via simple AI queries.
- Agile Teams — update task descriptions and check worklogs without leaving the workspace.
- Product Owners — monitor project progress and organization structure directly from the AI assistant.
Built-in capabilities (12)
Create a new task/story
Get account details
Get board details
Get item details
Get board worklogs
List items on a board
List all boards
List all organizations
List board sprints
List all teams
List configured webhooks
Update an item
Why VS Code Copilot?
GitHub Copilot Agent mode brings VivifyScrum 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.
- —
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
VivifyScrum in VS Code Copilot
VivifyScrum and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect VivifyScrum to VS Code Copilot 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 VivifyScrum in VS Code Copilot
The VivifyScrum 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 VS Code Copilot 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
VivifyScrum for VS Code Copilot
Every tool call from VS Code Copilot to the VivifyScrum MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I list all the tasks assigned to a specific board?
Yes! Use the list_board_items tool and provide the Board ID. Your agent will retrieve all tasks and stories for that project.
How do I see the active sprints for my project?
Run the list_sprints query with your Board ID. The agent will return a list of all sprints associated with that board, including their current status.
Is it possible to track time logs via AI?
Absolutely. Use the get_worklogs tool with your Board ID to retrieve the history of time tracking entries for that project.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .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.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.