GitScrum Knowledge

GitScrum Knowledge MCP Connector for Claude

A+

Build and query knowledge bases via GitScrum — manage notes as agent memory, maintain wiki pages, communicate through discussions, and search across all resources from any AI agent.

28 tools Official Updated Jun 28, 2026 Official Vinkius Partner

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

  1. Subscribe to the GitScrum Knowledge integration from the marketplace
  2. Enter your GitScrum API token and company slug
  3. 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
agent-memorywiki-documentationteam-discussionsknowledge-baseglobal-searchrevision-historynote-taking

28 tools expose this connector's capabilities to your AI agent.

create_channel

Create a discussion channel

get_channel

Get channel details

list_channels

List discussion channels

list_discussions

List all discussions in a project

create_note_folder

E.g., "Agent Memory", "Architecture Decisions", "Meeting Notes". Create a note folder

list_note_folders

Use folders to categorize agent memory by topic or project. List note folders

rename_note_folder

Rename a note folder

channel_messages

Get messages in a channel

search_channel_messages

Search messages in a channel

send_message

Useful for agents to communicate findings or status updates. Send a message to a channel

create_note

Use this as persistent agent memory: store decisions, context, meeting notes, or ADRs. Content supports full markdown. Create a new note

delete_note

Delete a note permanently

list_notes

Perfect for agent memory — store context, decisions, and key information across sessions. List all notes in the workspace

move_note_to_folder

Move a note into a folder

note_revisions

Useful for tracking how knowledge evolved over time. Get note revision history

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

reply_to_message

Reply to a message in a thread

global_search

Returns grouped results by resource type. Search across all workspace resources

thread_replies

Get thread replies for a message

create_wiki_page

Supports nested pages via parent_uuid. Create a wiki page

delete_wiki_page

Delete a wiki page

get_wiki_page

Get a wiki page with full content

list_wiki_pages

Wiki pages support markdown and nested hierarchies. List wiki pages in a project

restore_wiki_revision

Restore a wiki page to a previous revision

wiki_revisions

Get wiki page revision history

search_wiki

Search wiki pages

update_wiki_page

Update a wiki page

See how to talk to your AI agent using GitScrum Knowledge.

Save a note with today's architecture decision about using event sourcing.

Note created: 'ADR-007: Event Sourcing for Order Service' with your decision rationale in markdown. I've placed it in the 'Architecture Decisions' folder. The note is private — say 'share this note' when you're ready to publish it to the team.

Search everything in our workspace for 'payment gateway integration'.

Found 11 results across your workspace: 📋 3 tasks (WEB-28, WEB-31, WEB-40), 📚 2 wiki pages ('Payment Flow Architecture', 'Gateway Comparison'), 💬 4 discussion messages in #payments channel, 📝 2 notes ('Payment Provider Research', 'Stripe vs Adyen Analysis'). Want me to open any of these?

Post an update in the #engineering channel about today's deployment.

Message posted to #engineering: '🚀 Deployment complete — v2.4.1 is now live in production. Key changes: payment gateway integration, performance optimizations, and 3 bug fixes. Full changelog in the wiki.' The team will be notified. Want me to create a wiki page with the detailed changelog?

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.

Related Connectors