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

Name: GitScrum Knowledge
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 28 Tools Framework

Connect your CrewAI agents to GitScrum Knowledge through Vinkius, pass the Edge URL in the `mcps` parameter and every GitScrum Knowledge tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

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.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="GitScrum Knowledge Specialist",
    goal="Help users interact with GitScrum Knowledge effectively",
    backstory=(
        "You are an expert at leveraging GitScrum Knowledge tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in GitScrum Knowledge "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 28 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

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

When paired with CrewAI, GitScrum Knowledge becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call GitScrum Knowledge tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

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

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

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 28 tools from GitScrum Knowledge

Why Use CrewAI with the GitScrum Knowledge MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with GitScrum Knowledge through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

GitScrum Knowledge + CrewAI Use Cases

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

Automated multi-step research: a reconnaissance agent queries GitScrum Knowledge for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries GitScrum Knowledge, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain GitScrum Knowledge tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries GitScrum Knowledge against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

GitScrum Knowledge MCP Tools for CrewAI (28)

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

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

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

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

GitScrum Knowledge + CrewAI FAQ

Common questions about integrating GitScrum Knowledge MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.