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 Claude Desktop 28 tools — connect in under 2 minutes

Name: GitScrum Knowledge
Availability: InStock
Author: Vinkius

modelcontextprotocol.io/quickstart/user

Built by Vinkius GDPR 28 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

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": {
      // Your Vinkius token. get it at cloud.vinkius.com
      "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

Claude Desktop is the definitive way to connect GitScrum Knowledge to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 28 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

The GitScrum Knowledge MCP Server exposes 28 tools through the Vinkius. Connect it to Claude Desktop 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 Claude Desktop via MCP

Follow these steps to integrate the GitScrum Knowledge MCP Server with Claude Desktop.

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

Add the MCP Server

Paste the configuration above into the mcpServers section

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

Start using GitScrum Knowledge

Look for the 🔌 icon in the chat. your 28 tools are now available

Why Use Claude Desktop with the GitScrum Knowledge MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with GitScrum Knowledge through the Model Context Protocol.

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

GitScrum Knowledge + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the GitScrum Knowledge MCP Server delivers measurable value.

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

GitScrum Knowledge MCP Tools for Claude Desktop (28)

These 28 tools become available when you connect GitScrum Knowledge to Claude Desktop 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 Claude Desktop

Ready-to-use prompts you can give your Claude Desktop 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 Claude Desktop

Common issues when connecting GitScrum Knowledge to Claude Desktop through the Vinkius, and how to resolve them.

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.

GitScrum Knowledge + Claude Desktop FAQ

Common questions about integrating GitScrum Knowledge MCP Server with Claude Desktop.

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.