GitScrum Knowledge MCP Server for Cline 28 tools — connect in under 2 minutes
Cline is an autonomous AI coding agent inside VS Code that plans, executes, and iterates on tasks. Wire GitScrum Knowledge through Vinkius and Cline gains direct access to every tool. from data retrieval to workflow automation. without leaving the terminal.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
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.
{
"mcpServers": {
"gitscrum-knowledge": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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
Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including GitScrum Knowledge tool calls without waiting for prompts between steps. Connect 28 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.
The GitScrum Knowledge MCP Server exposes 28 tools through the Vinkius. Connect it to Cline 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 Cline via MCP
Follow these steps to integrate the GitScrum Knowledge MCP Server with Cline.
Open Cline MCP Settings
Click the MCP Servers icon in the Cline sidebar panel
Add remote server
Click "Add MCP Server" and paste the configuration above
Enable the server
Toggle the server switch to ON
Start using GitScrum Knowledge
Ask Cline: "Using GitScrum Knowledge, help me...". 28 tools available
Why Use Cline with the GitScrum Knowledge MCP Server
Cline provides unique advantages when paired with GitScrum Knowledge through the Model Context Protocol.
Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts
Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window
Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation
Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing
GitScrum Knowledge + Cline Use Cases
Practical scenarios where Cline combined with the GitScrum Knowledge MCP Server delivers measurable value.
Autonomous feature building: tell Cline to fetch data from GitScrum Knowledge and scaffold a complete module with types, handlers, and tests
Codebase refactoring: use GitScrum Knowledge tools to validate live data while Cline restructures your code to match updated schemas
Automated testing: Cline fetches real responses from GitScrum Knowledge and generates snapshot tests or mocks based on actual payloads
Incident response: query GitScrum Knowledge for real-time status and let Cline generate hotfix patches based on the findings
GitScrum Knowledge MCP Tools for Cline (28)
These 28 tools become available when you connect GitScrum Knowledge to Cline 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 Cline
Ready-to-use prompts you can give your Cline 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 Cline
Common issues when connecting GitScrum Knowledge to Cline through the Vinkius, and how to resolve them.
Server shows error in sidebar
GitScrum Knowledge + Cline FAQ
Common questions about integrating GitScrum Knowledge MCP Server with Cline.
How does Cline connect to MCP servers?
Can Cline run MCP tools without approval?
Does Cline support multiple MCP servers at once?
Connect GitScrum Knowledge with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect GitScrum Knowledge to Cline
Get your token, paste the configuration, and start using 28 tools in under 2 minutes. No API key management needed.