Wiki

Wiki management through MCP. Create, organize, and search project wiki pages for team documentation and knowledge bases.

Open Source — GitScrum MCP Server is open source under the MIT license. Available on npm and GitHub. Model Context Protocol server for GitScrum — Claude, GitHub Copilot, Cursor, and any MCP-compatible client full operational access to your project management stack.

The wiki tool provides 5 actions for creating, organizing, and searching project wiki pages. Wikis are your team's living documentation — onboarding guides, architecture decisions, API references, runbooks, and process documentation that stays within project context and evolves with the codebase.

Wiki pages support full Markdown content and hierarchical organization through parent-child relationships. Your AI assistant can create entire documentation structures, update existing pages, and search across wiki content — all through natural language conversation.

Actions Overview

Action	Purpose	Required Parameters
`list`	List all wiki pages in a project	`companyslug`, `project``slug`
`get`	Get full content of a specific wiki page	`uuid`, `companyslug`, `project``slug`
`create`	Create a new wiki page	`companyslug`, `project``slug`, `title`, `content`
`update`	Modify an existing wiki page's title or content	`uuid`, `companyslug`, `project``slug`
`search`	Search wiki content by keyword	`companyslug`, `project``slug`, `q`

Listing Wiki Pages

The list action returns all wiki pages within a project. Each page in the response includes its uuid, title, author, creation date, and parent page reference — giving you the full page tree structure.

Required Parameters

Parameter	Type	Description
`company_slug`	string	Workspace identifier (from the `workspace` tool)
`project_slug`	string	Project identifier (from the `project` tool)

You:  "List all wiki pages in the Backend project"
AI:   Calls wiki action=list → returns page tree with titles and hierarchy

You:  "Show me the documentation structure for the Mobile App project"
AI:   Calls wiki action=list → displays pages organized by parent-child relationships

You:  "What documentation exists in this project?"
AI:   Calls wiki action=list → summarizes available wiki pages

Getting Wiki Page Content

The get action returns the complete wiki page — title, content in Markdown, author, timestamps, and parent page reference. This is how you read a specific documentation page.

Required Parameters

Parameter	Type	Description
`uuid`	string	Wiki page UUID (from `list` or `search` response)
`company_slug`	string	Workspace identifier
`project_slug`	string	Project identifier

You:  "Show me the onboarding guide wiki page"
AI:   Finds page from list → calls wiki action=get → returns full Markdown content

You:  "Read the API reference documentation"
AI:   Calls wiki action=get → returns the complete page content

You:  "What does the deployment runbook say?"
AI:   Finds the page → calls wiki action=get → summarizes or displays the content

Creating Wiki Pages

The create action builds a new wiki page with a title and Markdown content. Pages can be created as top-level documentation or nested under a parent page to build hierarchical structures.

Required Parameters

Parameter	Type	Description
`company_slug`	string	Workspace identifier
`project_slug`	string	Project identifier
`title`	string	Page title — descriptive and scannable
`content`	string	Page body in Markdown format

Optional Parameters

Parameter	Type	Description
`parent_uuid`	string	Parent wiki page UUID to nest this page under. Omit for a top-level page.

Example Prompts

You:  "Create a wiki page 'Onboarding Guide' in the Backend project with
       setup instructions for new developers"
AI:   Calls wiki action=create with title and comprehensive Markdown content

You:  "Create a wiki page 'REST API Reference' documenting our endpoints"
AI:   Calls wiki action=create with title and structured API documentation

You:  "Add a child page 'Authentication Flow' under the Architecture section"
AI:   Finds Architecture page UUID → calls wiki action=create with parent_uuid

You:  "Create a deployment runbook covering staging and production procedures"
AI:   Calls wiki action=create with detailed step-by-step Markdown content

Nested Page Structures

Use parent_uuid to build documentation hierarchies. The AI assistant can create entire structures in a single conversation:

You:  "Create an Architecture wiki section with child pages for
       Database Design, API Layer, and Authentication"
AI:   1. Creates "Architecture" as top-level page
      2. Creates "Database Design" with parent_uuid of Architecture
      3. Creates "API Layer" with parent_uuid of Architecture
      4. Creates "Authentication" with parent_uuid of Architecture

Updating Wiki Pages

The update action modifies an existing wiki page. Only the fields you specify are changed — if you update just the content, the title remains untouched, and vice versa.

Required Parameters

Parameter	Type	Description
`uuid`	string	Wiki page UUID
`company_slug`	string	Workspace identifier
`project_slug`	string	Project identifier

Optional Parameters

Parameter	Type	Description
`title`	string	Updated page title
`content`	string	Updated page body in Markdown format

You:  "Update the onboarding guide with the new CI/CD pipeline instructions"
AI:   Finds page → calls wiki action=update with revised Markdown content

You:  "Rename the API docs page to 'REST API v3 Reference'"
AI:   Calls wiki action=update with title="REST API v3 Reference"

You:  "Add a section about error handling to the API reference wiki page"
AI:   Gets current content → appends new section → calls wiki action=update

Searching Wiki Content

The search action performs keyword search across all wiki pages in a project. Results include matching pages with their UUIDs and titles, allowing you to navigate directly to relevant documentation.

Required Parameters

Parameter	Type	Description
`company_slug`	string	Workspace identifier
`project_slug`	string	Project identifier
`q`	string	Search query (minimum 2 characters)

Optional Parameters

Parameter	Type	Description
`limit`	number	Maximum results to return (1-50)

You:  "Search the wiki for 'database migration'"
AI:   Calls wiki action=search with q="database migration" → returns matching pages

You:  "Find wiki pages about authentication"
AI:   Calls wiki action=search with q="authentication" → lists relevant documentation

You:  "Is there any documentation about the deployment process?"
AI:   Calls wiki action=search with q="deployment" → returns matching pages or empty

You:  "Search for 'API' in the project docs, show top 5 results"
AI:   Calls wiki action=search with q="API", limit=5

Knowledge Base Patterns

Wikis are most effective when organized around predictable patterns. Here are recommended structures for technical projects:

Project Documentation Structure

📄 Overview
  📄 Architecture
    📄 Database Design
    📄 API Layer
    📄 Authentication
  📄 Getting Started
    📄 Local Setup
    📄 Environment Variables
    📄 Running Tests
  📄 Deployment
    📄 Staging Runbook
    📄 Production Runbook
    📄 Rollback Procedures
  📄 API Reference
    📄 Endpoints
    📄 Error Codes
    📄 Rate Limits

Building the Structure

Your AI assistant can scaffold an entire documentation structure in one conversation:

You:  "Create a complete documentation wiki for the Backend project. Include
       sections for Architecture, Getting Started, Deployment, and API Reference.
       Each section should have relevant child pages."
AI:   Creates 10-15 wiki pages with hierarchical parent_uuid relationships,
      populating each with starter content

Keeping Documentation Current

Update pages as the codebase evolves. The search action helps find pages that need revision:

You:  "Search the wiki for references to the old auth endpoint"
AI:   Calls wiki action=search with q="auth" → identifies pages to update

You:  "Update all wiki pages that reference the v2 API to point to v3"
AI:   Searches → reads each page → updates references

Wiki vs Discussions vs NoteVault

Choose the right tool for the content type:

Aspect	Wiki (this tool)	Discussions	NoteVault
Scope	Project-level documentation	Project-level conversations	Personal/shared notes
Structure	Hierarchical pages	Threaded comments	Folder-organized notes
Lifecycle	Long-lived, evolves over time	Open → closed when resolved	Personal workspace
Best for	Onboarding guides, runbooks, references	Decisions, proposals, debates	Meeting notes, drafts, scratch

Context Auto-Resolution

The wiki tool supports automatic context resolution. If your AI assistant already knows the workspace and project from a previous call in the conversation, you can say "create a wiki page" without specifying the project — the context carries forward.

Next Steps

NoteVault: Manage personal and shared notes with folder organization.
Discussions: Create threaded discussion channels for team decisions.
Search: Search across all GitScrum entities including wiki pages.
Quick Start: Set up the MCP server if you haven't already.