GitHub Star Count MCP Server

Created By
JavaTheHutt1a year ago
MCP Server for GitHub
Overview

What is GitHub Star Count MCP Server?

GitHub Star Count MCP Server is a Model Context Protocol (MCP) server that allows users to fetch star counts from public GitHub repositories.

How to use GitHub Star Count MCP Server?

To use the server, clone the repository, install the necessary dependencies, set up your GitHub Personal Access Token, and run the server using the provided commands.

Key features of GitHub Star Count MCP Server?

  • Fetch star counts for any public GitHub repository.
  • Integrates seamlessly with Claude Desktop via MCP.
  • Simple API for retrieving repository statistics.

Use cases of GitHub Star Count MCP Server?

  1. Monitoring the popularity of GitHub repositories over time.
  2. Integrating star count data into applications for analytics.
  3. Providing insights into repository engagement for developers.

FAQ from GitHub Star Count MCP Server?

  • What are the prerequisites for running the server?

You need Python 3.11+, the uv dependency manager, and a GitHub Personal Access Token.

  • Is the server easy to set up?

Yes! The setup involves cloning the repository and running a few commands to install dependencies and configure your token.

  • Can I use this server for private repositories?

No, this server only fetches star counts for public GitHub repositories.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
JavaTheHutt1
Star
1
Language
Python
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago