Can my AI agent use notes as persistent memory across sessions?

Absolutely — this is a core design goal. Use `create_note` to store decisions, context, or meeting summaries as markdown notes. Organize them into folders with `create_note_folder` and `move_note_to_folder`. Use `toggle_note_share` to publish findings to the team. Every edit is versioned via `note_revisions` so you can track how knowledge evolves.

Can the agent search across everything in my workspace at once?

Yes! The `global_search` tool performs a unified search across tasks, wiki pages, discussions, user stories, sprints, and notes. Results are grouped by resource type, so you instantly see where every mention lives. It's the fastest way to find anything in your workspace.

Can the agent participate in team discussions and reply to threads?

Yes. Use `send_message` to post updates to any discussion channel, and `reply_to_message` for threaded conversations. The agent can also create channels with `create_channel`, search message history with `search_channel_messages`, and review thread replies with `thread_replies` — enabling fully automated status updates and knowledge sharing.

GitScrum Knowledge MCP Server for VS Code Copilot 28 tools — connect in under 2 minutes

Name: GitScrum Knowledge
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 28 Tools IDE

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.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install GitScrum Knowledge and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "gitscrum-knowledge": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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 GitScrum Knowledge MCP Server

What you can do

Agent memory via notes — create, update, share, and organize notes as persistent AI memory with full revision history and folder management
Wiki knowledge base — build and maintain project documentation with nested pages, markdown content, revision tracking, and restore capabilities
Team discussions — create channels, send messages, search conversations, and reply in threads for structured team communication
Global search — search across tasks, wiki pages, discussions, user stories, sprints, and notes in a single query
Knowledge versioning — track how information evolves over time with note and wiki revision histories

GitHub Copilot Agent mode brings GitScrum Knowledge data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 28 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

The GitScrum Knowledge MCP Server exposes 28 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.

How to Connect GitScrum Knowledge to VS Code Copilot via MCP

Follow these steps to integrate the GitScrum Knowledge MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using GitScrum Knowledge

Ask Copilot: "Using GitScrum Knowledge, help me...". 28 tools available

Why Use VS Code Copilot with the GitScrum Knowledge MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with GitScrum Knowledge 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

GitScrum Knowledge + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the GitScrum Knowledge 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

GitScrum Knowledge MCP Tools for VS Code Copilot (28)

These 28 tools become available when you connect GitScrum Knowledge to VS Code Copilot via MCP:

channel_messages

Get messages in a channel

create_channel

Create a discussion channel

create_note

Use this as persistent agent memory: store decisions, context, meeting notes, or ADRs. Content supports full markdown. Create a new note

create_note_folder

E.g., "Agent Memory", "Architecture Decisions", "Meeting Notes". Create a note folder

create_wiki_page

Supports nested pages via parent_uuid. Create a wiki page

delete_note

Delete a note permanently

delete_wiki_page

Delete a wiki page

get_channel

Get channel details

get_wiki_page

Get a wiki page with full content

global_search

Returns grouped results by resource type. Search across all workspace resources

list_channels

List discussion channels

list_discussions

List all discussions in a project

list_note_folders

Use folders to categorize agent memory by topic or project. List note folders

list_notes

Perfect for agent memory — store context, decisions, and key information across sessions. List all notes in the workspace

list_wiki_pages

Wiki pages support markdown and nested hierarchies. List wiki pages in a project

move_note_to_folder

Move a note into a folder

note_revisions

Useful for tracking how knowledge evolved over time. Get note revision history

rename_note_folder

Rename a note folder

reply_to_message

Reply to a message in a thread

restore_wiki_revision

Restore a wiki page to a previous revision

search_channel_messages

Search messages in a channel

search_wiki

Search wiki pages

send_message

Useful for agents to communicate findings or status updates. Send a message to a channel

thread_replies

Get thread replies for a message

toggle_note_share

Useful for publishing agent findings to the team. Toggle note sharing visibility

update_note

Use to append context or refine agent memory over time. Update an existing note

update_wiki_page

Update a wiki page

wiki_revisions

Get wiki page revision history

Example Prompts for GitScrum Knowledge in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with GitScrum Knowledge immediately.

"Save a note with today's architecture decision about using event sourcing."

"Search everything in our workspace for 'payment gateway integration'."

"Post an update in the #engineering channel about today's deployment."

Troubleshooting GitScrum Knowledge MCP Server with VS Code Copilot

Common issues when connecting GitScrum Knowledge to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

GitScrum Knowledge + VS Code Copilot FAQ

Common questions about integrating GitScrum Knowledge MCP Server with VS Code Copilot.

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.