GithubStats_MCP
Provides tools to fetch public GitHub user profiles, repository activity, events, and pull request insights.
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., "@GithubStats_MCP get stats for user torvalds"
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 MCP
A TypeScript-based Model Context Protocol (MCP) server for inspecting public GitHub data through tools that can be consumed by MCP-compatible clients such as Cursor or Claude Desktop.
What this project does
The server currently exposes two tools:
hello: returns a friendly greeting and serves as a simple protocol sanity check.github_user_stats: fetches a GitHub username’s public profile metadata, repository activity totals, recent public events, and pull request insights in one response.
The implementation uses the GitHub REST API to gather public profile information and formats the output into human-readable summaries.
Related MCP server: github-mcp
Features
Lightweight MCP server over stdio transport
Public GitHub profile and repository stats gathering
Pull request insights including:
total PR count
merged PR count
co-authored PR count
most targeted repository
Optional authentication via a GitHub token to reduce unauthenticated rate-limit issues
Test coverage for formatting and helper logic
Getting started
1. Install dependencies
git clone https://github.com/<your-username>/github_mcp.git
cd github_mcp
npm install2. Configure environment variables
Create a .env file in the project root if you want to use a GitHub token:
GITHUB_TOKEN=your_github_personal_access_tokenThis is optional, but recommended for smoother API usage.
3. Run the server
npm run devThe server runs over stdio, so stdout is reserved for MCP protocol traffic and logs are written to stderr.
Example tool calls
Hello
{
"name": "Mahesh"
}GitHub stats
{
"username": "Maheshkumarjena"
}Scripts
npm run devstarts the MCP server in development modenpm run buildcompiles the TypeScript projectnpm testruns the Vitest test suite
Project structure
src/index.tsbootstraps the MCP serversrc/tools.tsregisters the available MCP toolssrc/github.tswraps GitHub API requests and data aggregationsrc/schemas.tsdefines tool input validation with Zodsrc/types.tscontains shared TypeScript interfacessrc/utils.tsformats and transforms data for outputtests/contains unit tests for helper behavior
Development notes
The current implementation is intentionally small and focused on a solid foundation for GitHub data access. It is a good starting point for adding more GitHub endpoints and exposing additional MCP tools.
Contributing
Fork the repository
Create a feature branch
Extend the GitHub client in
src/github.tsor add new tools insrc/tools.tsRun
npm testandnpm run buildbefore opening a pull request
Available Tools
2 toolsgithub_user_statsB
Fetch public GitHub profile, activity stats, and pull request insights.
Inputs: username (required).
helloA
Return a friendly greeting for the provided name.
Inputs: name.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools are entirely distinct: 'hello' provides a greeting, while 'github_user_stats' fetches GitHub data. There is no overlap or ambiguity between them.
The tool names lack a consistent pattern. 'hello' is a simple interjection, while 'github_user_stats' is a compound noun; neither follows a verb_noun convention, making the naming style inconsistent.
With only two tools, one of which is a generic greeting, the set feels thin for a GitHub stats server. However, it is not an extreme mismatch given the narrow domain.
The 'github_user_stats' tool covers the primary domain of fetching user profile, activity, and PR insights, but the inclusion of 'hello' adds no domain value, and there is no ability to query specific metrics or historical data, leaving minor gaps.
Maintenance
Related MCP Connectors
An MCP server that gives your AI access to the source code and docs of all public github repos
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…
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
Related MCP Servers
- AlicenseBqualityCmaintenanceMCP server that exposes GitHub operations as tools for AI agents, enabling code search, issue management, and PR review.12MIT
- FlicenseNot gradedqualityDmaintenanceA read-only MCP server that exposes GitHub user profiles, repository info, and search via tools for AI assistants like Claude.-
- FlicenseAqualityCmaintenanceMCP server for exploring GitHub public data. It provides tools to fetch user profiles, list top repositories, and calculate language usage statistics, which AI agents can invoke dynamically.3-
- AlicenseAqualityDmaintenanceA lightweight MCP server that exposes GitHub tools for searching repositories, listing issues, and reading file contents.3456 npmISC