Skip to main content
Glama
Sign In
GitHub Portfolio MCP Server

GitHub Portfolio MCP Server

by bdbrown4
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

GitHub Portfolio MCP Server

An MCP (Model Context Protocol) server that exposes tools for AI agents to query a GitHub user's public profile, repositories, languages, and README content.

Tools

Tool

Description

list_repos

List all public repositories with optional fork filtering and sorting

get_repo_details

Get detailed info about a repo including its full README

get_languages

Get language breakdown (with percentages) for a repository

get_profile

Get the GitHub user's public profile (bio, location, stats)

search_repos

Search repos by keyword across names, descriptions, and topics

get_tech_stack_summary

Aggregate languages and topics across all original repos

Related MCP server: GitBridge

Resources

Resource

URI

Description

Profile

github://bdbrown4/profile

Full GitHub profile JSON

README

github://{owner}/{repo}/readme

README content for any repo

Setup

npm install
npm run build

Usage with Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "github-portfolio": {
      "command": "node",
      "args": ["C:/dev/github-portfolio-mcp-server/dist/index.js"]
    }
  }
}

Usage with VS Code (GitHub Copilot)

Add to your .vscode/mcp.json or user settings:

{
  "servers": {
    "github-portfolio": {
      "command": "node",
      "args": ["C:/dev/github-portfolio-mcp-server/dist/index.js"]
    }
  }
}

Optional: Higher Rate Limits

Set a GitHub Personal Access Token to avoid the 60 req/hour unauthenticated limit:

{
  "mcpServers": {
    "github-portfolio": {
      "command": "node",
      "args": ["C:/dev/github-portfolio-mcp-server/dist/index.js"],
      "env": {
        "GITHUB_TOKEN": "ghp_your_token_here"
      }
    }
  }
}

Example

Here's the list_repos tool in action inside VS Code with GitHub Copilot, listing all 18 original (non-forked) public repos sorted by most recently updated:

list_repos example

Development

npm run dev    # Watch mode — recompiles on change
npm run build  # One-time compile
npm start      # Run the server (stdio)

Available Tools

6 tools
get_languagesGet Repository LanguagesB

Get programming languages used in a repository with byte counts.

Inputs: repo_name (required).

get_profileGet GitHub ProfileA

Get the public GitHub profile for bdbrown4.

Inputs: no named parameters.

get_repo_detailsGet Repository DetailsA

Get detailed info about a specific repository including its README.

Inputs: repo_name (required).

get_tech_stack_summaryTech Stack SummaryA

Aggregate languages and technologies across all of bdbrown4's repos.

Inputs: no named parameters.

list_reposList GitHub RepositoriesC

List public repositories for bdbrown4.

Inputs: sort, include_forks.

search_reposSearch RepositoriesA

Search bdbrown4's repositories by keyword.

Inputs: query (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.8/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool serves a clear, distinct purpose: listing repos, getting specific repo details, languages, profile, searching, and tech stack aggregation. Overlap between list_repos and search_repos is minimal since search is a filtered view, and get_languages vs get_tech_stack_summary differ by scope (single repo vs aggregate).

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., list_repos, get_profile, search_repos). Even the longer get_tech_stack_summary adheres to the same convention, making the set predictable and easy to navigate.

    Tool Count5/5

    Six tools is well-scoped for a portfolio-focused server. The count is neither too sparse nor too heavy, and each tool contributes a necessary function for showcasing a GitHub profile and repos.

    Completeness5/5

    The tool surface fully covers the apparent domain of a GitHub portfolio: listing repos, viewing details, checking languages, profile info, searching, and summarizing tech stack. There are no obvious dead ends or missing operations for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers

    Appeared in Searches