enable_github_pagesLABSCO SUMMARY
The Pages settings screen, reachable without opening the Pages settings screen.
Everything here is a repository-settings operation — which branch and folder publish, which builder runs, which domain answers — so a site can go from off to live, or be repointed, in the same place you are already talking about the repository.
What it is
A server over the GitHub Pages API: enable or disable Pages for a repository, read its current configuration, change the source, and deploy files to the Pages branch.
What you get
- Pages enabled for a repository with the branch and path you name
- A choice between Jekyll and a GitHub Actions workflow as the build type
- The current Pages configuration and deployment status read back
- Files deployed straight to the Pages branch
- Source, build type and custom domain changed after the fact
- Pages switched off again for a repository
Requirements
A GitHub personal access token carrying the repo and public_repo scopes, plus workflow if you use the Actions build type. Node, with the project built locally before first use.
Setup effort
Build from source
USE CASES
01
Publishing docs that are already in the repo
Enable Pages on the branch and the /docs path in one call, and let Jekyll build it.
02
Finding out why a site is not updating
Read the current configuration and deployment status before changing anything — the source branch is usually the answer.
03
Moving a site onto your own domain
Update the configuration with the custom domain, and confirm it took by reading the config back.
04
Switching a site from Jekyll to Actions
Change the build type to the workflow builder, which needs the workflow scope on your token.
05
Taking a site down
Disable Pages for the repository rather than deleting the branch and hoping.
5 tools
Listed in project docs. Your client may show a different list.
get_github_pages_infodeploy_to_github_pagesdisable_github_pagesupdate_github_pages_configBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Requires
- Node.js >= 18.0.0
- GITHUB_TOKEN in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/ajaychinthapalli/github-pages-mcp-server
cd github-pages-mcp-server
npm install
npm run buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"github-pages": {
"command": "node",
"args": [
"<YOUR_PATH_TO_GITHUB_PAGES_MCP_SERVER>/dist/index.js"
],
"env": {
"GITHUB_TOKEN": "<YOUR_GITHUB_TOKEN>"
}
}
}
}
