github-wiki-mcp
Provides tools for managing GitHub wiki pages, including creating, reading, appending, listing, and deleting pages in a GitHub repository.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@github-wiki-mcp Create a wiki page called 'Home' with welcome content for myrepo."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
GitHub Wiki MCP Server
MCP (Model Context Protocol) server for managing GitHub wiki pages programmatically.
Features
This MCP server exposes the following tools:
write_wiki_page- Create or update a wiki pageread_wiki_page- Read the content of a wiki pageappend_to_wiki_page- Append content to an existing pagelist_wiki_pages- List all wiki pages in the repositorydelete_wiki_page- Delete a wiki page
Related MCP server: wikijs-mcp-server
Installation
# Install dependencies
pnpm install
# Build the TypeScript project
pnpm buildConfiguration
1. Create a GitHub Personal Access Token
Go to GitHub → Settings → Developer settings → Personal access tokens → Tokens (classic)
Click "Generate new token (classic)"
Select the
reposcope (to access repository wikis)Copy the generated token
2. Add the MCP server to Claude Desktop configuration
Edit the configuration file:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
Add this configuration:
{
"mcpServers": {
"github-wiki": {
"command": "node",
"args": [
"/absolute/path/to/github_wiki_mcp/dist/index.js"
]
}
}
}Replace /absolute/path/to/github_wiki_mcp with the actual path to the project directory.
3. Restart Claude Desktop
Close and reopen Claude Desktop to load the new MCP server.
Usage
Example: Write a wiki page about architecture
You can tell Claude:
Analyze the codebase using code-analysis-context-mcp to extract
all information about the repository architecture and write
a dedicated wiki page on GitHub called Architecture.Claude will:
Use the
code_analysistool to get architecture informationGenerate structured markdown content
Use
write_wiki_pageto create the page on GitHub
Direct Example: Create a wiki page
Create a wiki page called "API Documentation" on the repository
myusername/myrepo with this content:
# API Documentation
## Main Endpoints
- GET /api/users
- POST /api/users
- DELETE /api/users/:idExample: Read an existing page
Read the content of the wiki page "Architecture" from the repository
myusername/myrepoExample: Update an existing page
Add a "Deployment" section to the wiki page "Architecture"
with deployment instructionsTool Reference
write_wiki_page
Creates or completely overwrites a wiki page.
Parameters:
owner(string, required): GitHub username or organizationrepo(string, required): Repository nametoken(string, required): GitHub personal access tokenpageName(string, required): Page name (e.g., "Architecture")content(string, required): Markdown content of the pagecommitMessage(string, optional): Custom commit message
Output:
{
"success": true,
"page": "Architecture.md",
"url": "https://github.com/owner/repo/wiki/Architecture"
}read_wiki_page
Reads the content of an existing wiki page.
Parameters:
owner,repo,token: Same as abovepageName(string, required): Name of the page to read
Output:
{
"success": true,
"page": "Architecture.md",
"content": "# Architecture\n\n..."
}append_to_wiki_page
Appends content to the end of an existing page (or creates it if it doesn't exist).
Parameters:
owner,repo,token: Same as abovepageName(string, required): Page namecontent(string, required): Content to appendcommitMessage(string, optional): Commit message
list_wiki_pages
Lists all wiki pages in the repository.
Parameters:
owner,repo,token: Same as above
Output:
[
{
"name": "Architecture",
"path": "Architecture.md",
"size": 2048
},
{
"name": "API-Documentation",
"path": "API-Documentation.md",
"size": 1024
}
]delete_wiki_page
Deletes a wiki page.
Parameters:
owner,repo,token: Same as abovepageName(string, required): Name of the page to deletecommitMessage(string, optional): Commit message
How It Works
The server uses the wiki Git repository (.wiki.git) instead of GitHub's REST API:
Clones the wiki repository to a temporary directory
Performs the requested operations (create/modify/delete
.mdfiles)Commits and pushes the changes
Cleans up the temporary directory
This approach:
Is more reliable than REST APIs for wikis
Supports all standard Git operations
Has no content size limitations
Works with private repositories (if the token has permissions)
Integration with Other MCPs
With code-analysis-context-mcp
You can combine this server with your code-analysis-context-mcp to:
Automatically analyze the codebase
Extract documentation, architecture, APIs
Automatically write updated wiki pages
Example workflow:
Analyze the repository using code-analysis-context-mcp,
extract the complete architecture and create three wiki pages:
1. Architecture - overall project structure
2. API - endpoint documentation
3. Database - schema and relationshipsClaude will use:
code_analysis.get_repository_architecture→ analysisgithub_wiki.write_wiki_page→ Architecture pagegithub_wiki.write_wiki_page→ API pagegithub_wiki.write_wiki_page→ Database page
Security
Never share your GitHub token: The token has full access to repositories
Use tokens with minimum scope: Only
repois necessaryConsider using expiring tokens: For production environments
Don't commit the token: Ensure it's only provided at runtime
Development
# Watch mode during development
pnpm dev
# Production build
pnpm build
# Local installation for testing
pnpm linkTroubleshooting
Server doesn't connect
Verify that the path in
claude_desktop_config.jsonis absolute and correctCheck that
pnpm buildhas been executedVerify Claude Desktop logs
Authentication error
Verify that the GitHub token is valid
Check that the token has the
reposcopeEnsure the repository has wiki enabled (Settings → Wiki)
Wiki doesn't exist
GitHub automatically creates the wiki repository only when the first page is created manually. If the repository has never had a wiki:
Go to
https://github.com/owner/repo/wikiClick "Create the first page"
Create a test page
Now the MCP server will be able to access the wiki
License
MIT
Available Tools
5 toolsappend_to_wiki_pageA
Append content to an existing wiki page. If the page does not exist, creates it with the provided content.
Inputs: repo (required), owner (required), token (required), content (required), +2 more.
delete_wiki_pageB
Delete a wiki page from a GitHub repository wiki.
Inputs: repo (required), owner (required), token (required), pageName (required), +1 more.
list_wiki_pagesA
List all wiki pages in a GitHub repository wiki.
Inputs: repo (required), owner (required), token (required).
read_wiki_pageA
Read the content of an existing GitHub wiki page.
Inputs: repo (required), owner (required), token (required), pageName (required).
write_wiki_pageA
Write or update a GitHub wiki page. Creates a new page or overwrites an existing one with the provided content.
Inputs: repo (required), owner (required), token (required), content (required), +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool targets a distinct operation on wiki pages: write overwrites, read retrieves, append adds content, list enumerates, delete removes. There is no overlap or ambiguity among these operations, even though append can create a missing page, it is clearly distinct from write.
All tools follow a verb_noun pattern (write_wiki_page, read_wiki_page, list_wiki_pages, delete_wiki_page), with append_to_wiki_page being the only minor deviation but still consistent in style. The pattern is predictable and clear.
Five tools is an ideal size for a wiki page manager, providing all core operations without unnecessary bloat. Each tool earns its place in the set, and the scope is tightly focused.
The set covers the full CRUD lifecycle: create/write, read, update/append, list, and delete. All essential wiki page management operations are present, with no obvious gaps for the stated purpose.
Maintenance
Related MCP Connectors
Create, deploy, and operate MCP servers directly from your GitHub repositories.
A MCP server built for developers enabling Git based project management with project and personal…
Shared project wiki for AI agents: read and write pages, next actions, and activity logs over MCP.
MCP server for accessing curated awesome list documentation
Related MCP Servers
- -licenseNot gradedqualityBmaintenanceMCP Server for the GitHub API, enabling file operations, repository management, search functionality, and more.127,455 npm91,952MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for Wiki.js integration, enabling AI assistants to create, read, update, delete, search, and move wiki pages via natural language.1MIT
- AlicenseAqualityDmaintenanceAn MCP server for managing Wiki.js 2.x pages through its GraphQL API, enabling search, read, create, update, move, delete, version history, and asset listing.1364 npmMIT
- AlicenseNot gradedqualityNot gradedmaintenanceMCP server for the GitHub API, enabling file operations, repository management, search functionality, issues, pull requests, and more.317 npmMIT