Enables interaction with Git repositories for version control operations like cloning and pushing changes.
Provides tools for working with GitHub repositories, including forking, creating pull requests, and managing branches.
Supports publishing content to GitHub Pages from a dedicated branch (gh-pages) to create web content.
Enables creation and rendering of Markdown content within repository documentation.
Click on "Install 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., "@ddd list recent commits in the test repository"
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.
Hey! This is my personal Git(Hub) Test Repository where I experiment with Git and GitHub.
If you are new to Git and GitHub and found this repository through Google: feel free to clone the repository and experiment with it! You will not be able to push back to the repository, as it is my repository and I cannot let everybody push to it. The right way to do it on GitHub is:
fork the repository in your own account,
make changes and push them in a branch of your own fork,
create a Pull Request in my repository.
I will get notified, will review the changes that you propose, and eventually will either merge the changes, or reject them. This may take some time as I am not actively monitoring nor maintaining this repository, as you can guess, but I try to be helpful ;)
If you want your PR to have a chance to get merged, please propose additions or changes to neutral files such as text files or small images. If you propose changes to the GitHub workflow files, to.gitignore, etc. they will quite probably be rejected.
New in 2026! Up until now I had to reject most PRs as they were either adding new files, or modifying files that I would rather not modify. There is now aRANDOM.md file at the top of the repository: I do not care what goes into that file. If your PR targets that file only, and is OK-enough (no profanity, no... you know) I will try to merge it. OK and... you want to add files? Let us say we do the same with the random directory: anything OK-enough proposed in that directory will be merged. Enjoy!
Don't expect to find anything meaningful nor useful in the repository. Also, I happen to force-push a reset of everything from time to time. This means that I reset all history, including changes that you may have submitted. In theory, noone ever does this to a repository. But hey, this is a test repository after all.
The rest of this README file is mostly random stuff.
Clone the repository with: git clone https://github.com/zpqrtbnk/test-repo.git .
We have test GitHUb pages (from the gh-pages branch) at: http://zpqrtbnk.github.io/test-repo/
We have an image in the README (markdown)
We have an image in the README (html)
We have an image in the README (more html)
This server cannot be installed
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Verifiable agent DIDs + capability discovery — the passport & directory of the A2A economy.
One MCP: hosted Pix receive + dated charges (22 tools), or local npx non-custodial wallet (49).
327 tools, 92 providers. Pay per call via x402 + MPP. One MCP endpoint.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/zpqrtbnk/test-repo'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
