Bring Agent Memory
to Cursor
Create your Vinkius account to connect GitScrum Knowledge to Cursor and start using all 28 AI tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code. No hosting, no server setup — just connect and start using.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the 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
How it works
- Subscribe to the GitScrum Knowledge integration from the marketplace
- Enter your GitScrum API token and company slug
- Use your agent as a knowledge hub — store decisions in notes, document processes in wiki, discuss with the team, and search everything in natural language
Your agent becomes the central knowledge repository, bridging personal memory with team knowledge.
Who is this for?
- AI practitioners — maintain persistent agent memory across sessions using notes as structured context
- Technical writers — manage wiki documentation with version control and search directly through conversation
- Team leads — foster asynchronous team communication and decision-tracking without platform switching
Built-in capabilities (28)
Get messages in a channel
Create a discussion channel
Use this as persistent agent memory: store decisions, context, meeting notes, or ADRs. Content supports full markdown. Create a new note
E.g., "Agent Memory", "Architecture Decisions", "Meeting Notes". Create a note folder
Supports nested pages via parent_uuid. Create a wiki page
Delete a note permanently
Delete a wiki page
Get channel details
Get a wiki page with full content
Returns grouped results by resource type. Search across all workspace resources
List discussion channels
List all discussions in a project
Use folders to categorize agent memory by topic or project. List note folders
Perfect for agent memory — store context, decisions, and key information across sessions. List all notes in the workspace
Wiki pages support markdown and nested hierarchies. List wiki pages in a project
Move a note into a folder
Useful for tracking how knowledge evolved over time. Get note revision history
Rename a note folder
Reply to a message in a thread
Restore a wiki page to a previous revision
Search messages in a channel
Search wiki pages
Useful for agents to communicate findings or status updates. Send a message to a channel
Get thread replies for a message
Useful for publishing agent findings to the team. Toggle note sharing visibility
Use to append context or refine agent memory over time. Update an existing note
Update a wiki page
Get wiki page revision history
Why Cursor?
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.
- —
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 in Cursor
Why run GitScrum Knowledge with Vinkius?
The GitScrum Knowledge connection runs on our fully managed, secure cloud infrastructure. We handle the hosting, maintenance, and security so you don't have to deal with servers or code. All 28 tools are ready to work instantly without any complex setup.
You stay in complete control of your data. Your AI only accesses the information you approve, keeping your sensitive passwords and private details completely safe. Plus, with automatic optimizations, your AI works faster and more efficiently.
* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure
Over 4,000 integrations ready for AI agents
Explore a vast library of pre-built integrations, optimized and ready to deploy.
Connect securely in under 30 seconds
Generate tokens to authenticate and link external services in a single step.
Complete visibility into every agent action
Audit live requests, latency, success rates, and active security compliance policies.
Optimize spending and track token ROI
Analyze real-time token consumption and cost metrics detailed by connection.
Explore our live AI Agents Analytics dashboard to see it all working
This dashboard is included when you connect GitScrum Knowledge using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.
GitScrum Knowledge and 4,000+ other AI tools. No hosting, no code, ready to use.
Professionals who connect GitScrum Knowledge to Cursor through Vinkius don't need to write code, manage servers, or worry about security. Everything is pre-configured, secure, and runs automatically in the background.
Raw MCP | Vinkius | |
|---|---|---|
| Ready-to-use MCPs | Find and configure each manually | 4,000+ MCPs ready to use |
| Connection Setup | Manual coding & server setup | 1-click instant connection |
| Server Hosting | You host it yourself (needs 24/7 uptime) | 100% hosted & managed by Vinkius |
| Security & Privacy | Stored in plaintext config files | Bank-grade encrypted vault |
| Activity Visibility | Blind execution (no logs or tracking) | Live dashboard with real-time logs |
| Cost Control | Runaway AI token spend risk | Automatic budget limits |
| Revoking Access | Must delete files or code to stop | 1-click disconnect button |
How Vinkius secures
GitScrum Knowledge for Cursor
Every request between Cursor and GitScrum Knowledge is protected by our secure gateway. We automatically keep your sensitive data private, prevent unauthorized access, and let you disconnect instantly at any time.
Frequently asked questions
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.
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.
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.
Explore More MCP Servers
View all →
Atlassian Crowd
10 toolsEquip your AI agent to manage users, groups, and directory memberships via the Atlassian Crowd API.
Docamatic
8 toolsGenerate professional PDFs from templates with dynamic data injection for invoices, reports, and custom documents at scale.
PagerDuty Incident Trigger
1 toolsThis MCP does exactly one thing: it triggers incidents in PagerDuty. That's its only function, and nothing else. Incredible for giving your AI agents the power to wake up engineers.
Google Analytics 4
12 toolsUnderstand your website and app traffic with event-based analytics that reveal user behavior, conversions, and growth trends.