Skip to main content
Glama
Maheshkumarjena

GithubStats_MCP

by Maheshkumarjena
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

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 install

2. 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_token

This is optional, but recommended for smoother API usage.

3. Run the server

npm run dev

The 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 dev starts the MCP server in development mode

  • npm run build compiles the TypeScript project

  • npm test runs the Vitest test suite

Project structure

  • src/index.ts bootstraps the MCP server

  • src/tools.ts registers the available MCP tools

  • src/github.ts wraps GitHub API requests and data aggregation

  • src/schemas.ts defines tool input validation with Zod

  • src/types.ts contains shared TypeScript interfaces

  • src/utils.ts formats and transforms data for output

  • tests/ 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

  1. Fork the repository

  2. Create a feature branch

  3. Extend the GitHub client in src/github.ts or add new tools in src/tools.ts

  4. Run npm test and npm run build before opening a pull request

Available Tools

2 tools
github_user_statsB

Fetch public GitHub profile, activity stats, and pull request insights.

ParametersJSON Schema
NameRequiredDescriptionDefault
usernameYesGitHub username

TDQS

B3.3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention potential side effects, authentication requirements, rate limits, or the exact structure of returned data. The description only names the data categories, leaving the behavioral expectations largely unspecified.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no filler. It efficiently communicates the core purpose without wasting words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only one parameter and no output schema, the description gives a high-level view of what is returned ('profile, activity stats, and pull request insights') but lacks specifics on the output format, error cases, or any limitations. It is adequate for a basic fetch tool but leaves gaps in completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already provides full coverage for the single parameter 'username' with its description. The tool description adds no extra meaning about the parameter beyond what the schema states. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific verb ('Fetch') and a resource ('public GitHub profile, activity stats, and pull request insights'). This distinguishes the tool from its sibling 'hello', which appears unrelated. The purpose is immediately understandable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. It simply states what the tool does without contextual usage instructions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

helloA

Return a friendly greeting for the provided name.

ParametersJSON Schema
NameRequiredDescriptionDefault
nameNoName to greetMahesh

TDQS

A4.4/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description alone conveys the tool's behavior. 'Return a friendly greeting' fully discloses a pure, side-effect-free operation; there is no hidden state change, authentication, or rate limiting. Nothing more is needed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with zero filler words. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is extremely simple with one optional parameter and no output schema. The description adequately explains the action, and the missing return value format is a minor detail that the agent can infer. A 4 reflects the slight uncertainty about the exact greeting phrasing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% (the property already has a description, default, and type). The description only restates 'provided name' without adding extra meaning, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the exact verb ('Return') and resource ('a friendly greeting'), with the input scope ('for the provided name'). It is entirely unambiguous and distinguishes itself from the unrelated sibling tool github_user_stats.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly implies usage: call this when you need a greeting for a given name. There are no alternatives or exclusions, but for such a simple tool the context is self-evident, earning a 4 rather than a 3.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 2 tool updatesv0.1.0
    • First observedgithub_user_stats
    • First observedhello
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.6/5.0
Disambiguation5/5

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.

Naming Consistency2/5

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.

Tool Count3/5

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.

Completeness4/5

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

ActivitySlowing
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Maheshkumarjena/GithubStats_MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server