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

Name: GitScrum Knowledge
Availability: InStock
Author: Vinkius

docs.cursor.com/context/model-context-protocol

Built by Vinkius GDPR 28 Tools IDE

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

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

Cursor's Agent mode turns GitScrum Knowledge into an in-editor superpower. Ask Cursor to generate code using live data from GitScrum Knowledge and it fetches, processes, and writes. all in a single agentic loop. 28 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

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

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

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"

Add the server config

Paste the JSON configuration above into the mcp.json file that opens

Save the file

Cursor will automatically detect the new MCP server

Start using GitScrum Knowledge

Open Agent mode in chat and ask: "Using GitScrum Knowledge, help me...". 28 tools available

Why Use Cursor with the GitScrum Knowledge MCP Server

Cursor AI Code Editor provides unique advantages when paired with GitScrum Knowledge through the Model Context Protocol.

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

GitScrum Knowledge + Cursor Use Cases

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

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

GitScrum Knowledge MCP Tools for Cursor (28)

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

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

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

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

GitScrum Knowledge + Cursor FAQ

Common questions about integrating GitScrum Knowledge MCP Server with Cursor.

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.