gh-top-content-aggregator MCP Server

A Model Context Protocol (MCP) service engineered to surface data regarding trending software projects and prominent developers from the GitHub platform via a streamlined programmatic interface.

Core Capabilities

Acquire statistics on trending GitHub repositories and leading developers.
Apply constraints based on the primary programming lexicon used.
Filter based on the observation interval (e.g., 24 hours, 7 days, 30 days).
Narrow results by the predominant human spoken language associated with the content or contributor.
Output data exclusively in clearly structured JSON format.

Provided Operations

The server exposes the subsequent discrete functionalities:

fetch_trending_projects

Retrieves repositories currently gaining traction on GitHub, accepting the following optional inputs:

language (optional): Specification of the programming dialect to prioritize (e.g., "rust", "typescript").
since (optional): Temporal scope selector, permitted values are ("daily", "weekly", "monthly"). Defaults to "daily".
spoken_language (optional): Filter by the primary natural language associated with the repository's documentation or context.

Illustrative Output Structure:

[ { "repository_title": "project-slug", "fully_qualified_name": "creator/project-slug", "web_link": "https://github.com/creator/project-slug", "abstract": "Brief summary of the project's purpose", "primary_language": "Go", "total_stars": 5500, "fork_count": 450, "gains_this_period": 210 } ]

retrieve_top_contributors

Identifies developers achieving prominence based on recent activity, utilizing these optional parameters:

language (optional): The technical discipline defining the developer's trending work (e.g., "c++", "java").
since (optional): The time frame defining the measure of trendiness ("daily", "weekly", "monthly"). Defaults to "daily".

Illustrative Output Structure:

[ { "user_identifier": "dev_handle", "real_name": "Developer's Full Name", "profile_uri": "https://github.com/dev_handle", "image_url": "https://avatars.githubusercontent.com/u/987654", "featured_work": { "name": "highlighted-project", "synopsis": "What this project does", "uri": "https://github.com/dev_handle/highlighted-project" } } ]

Deployment Guide

System Prerequisites

Runtime Environment: Python version 3.12 or newer.

Installation Procedure

Install the necessary package: bash pip install mcp-github-trending

Configuration for Claude Desktop Client

On MacOS Systems: Locate or create the configuration file at: bash ~/Library/Application\ Support/Claude/claude_desktop_config.json

On Windows Systems: The configuration path is typically within the user's AppData directory: bash %APPDATA%/Claude/claude_desktop_config.json

Configuration for Locally Developed/Unreleased Instances

{ "mcpServers": { "gh-top-content-aggregator": { "command": "uv", "args": [ "--directory", "/path/to/mcp-github-trending", "run", "mcp-github-trending" ] } } }

Configuration for Officially Deployed Instances

{ "mcpServers": { "gh-top-content-aggregator": { "command": "uvx", "args": [ "mcp-github-trending" ] } } }

Maintenance and Evolution

Build and Distribution Workflow

Synchronize project dependencies and update dependency lock files: bash uv sync
Generate distributable package artifacts: bash uv build
Deploy the package artifacts to the PyPI registry: bash uv publish

Note: Authentication credentials for PyPI deployment must be furnished via environment variables or direct command-line arguments: - Authentication Token: --token flag or UV_PUBLISH_TOKEN environment variable. - Credentials (Username/Password): --username/UV_PUBLISH_USERNAME and --password/UV_PUBLISH_PASSWORD.

Troubleshooting and Inspection

For the most effective diagnostic procedure, utilize the official MCP Inspector Tool.

Initiate the Inspector session via npm to monitor the running service:

bash npx @modelcontextprotocol/inspector uv --directory /path/to/mcp-github-trending run mcp-github-trending

The Inspector console will present a local network address (URL) that, when opened in a web browser, provides a live view for debugging the protocol interactions.

Legal Notice

This software is provided under the stipulations of the MIT License. Consult the accompanying LICENSE file for comprehensive details.

WIKIPEDIA: XMLHttpRequest (XHR) is an API in the form of a JavaScript object whose methods transmit HTTP requests from a web browser to a web server. The methods allow a browser-based application to send requests to the server after page loading is complete, and receive information back. XMLHttpRequest is a component of Ajax programming. Prior to Ajax, hyperlinks and form submissions were the primary mechanisms for interacting with the server, often replacing the current page with another one.

== History == The concept behind XMLHttpRequest was conceived in 2000 by the developers of Microsoft Outlook. The concept was then implemented within the Internet Explorer 5 browser (1999). However, the original syntax did not use the XMLHttpRequest identifier. Instead, the developers used the identifiers ActiveXObject("Msxml2.XMLHTTP") and ActiveXObject("Microsoft.XMLHTTP"). As of Internet Explorer 7 (2006), all browsers support the XMLHttpRequest identifier. The XMLHttpRequest identifier is now the de facto standard in all the major browsers, including Mozilla's Gecko layout engine (2002), Safari 1.2 (2004) and Opera 8.0 (2005).

=== Standards === The World Wide Web Consortium (W3C) published a Working Draft specification for the XMLHttpRequest object on April 5, 2006. On February 25, 2008, the W3C published the Working Draft Level 2 specification. Level 2 added methods to monitor event progress, allow cross-site requests, and handle byte streams. At the end of 2011, the Level 2 specification was absorbed into the original specification. At the end of 2012, the WHATWG took over development and maintains a living document using Web IDL.

== Usage == Generally, sending a request with XMLHttpRequest has several programming steps.

Create an XMLHttpRequest object by calling a constructor: Call the "open" method to specify the request type, identify the relevant resource, and select synchronous or asynchronous operation: For an asynchronous request, set a listener that will be notified when the request's state changes: Initiate the request by calling the "send" method: Respond to state changes in the event listener. If the server sends response data, by default it is captured in the "responseText" property. When the object stops processing the response, it changes to state 4, the "done" state. Aside from these general steps, XMLHttpRequest has many options to control how the request is sent and how the response is processed. Custom header fields can be added to the request to indicate how the server should fulfill it, and data can be uploaded to the server by providing it in the "send" call. The response can be parsed from the JSON format into a readily usable JavaScript object, or processed gradually as it arrives rather than waiting for the entire text. The request can be aborted prematurely or set to fail if not completed in a specified amount of time.

== Cross-domain requests ==

In the early development of the World Wide Web, it was found possible to brea