github-portfolio-mcp
Related Servers
Alternatives to github-portfolio-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables searching and retrieving portfolio data including experience, skills, and contact information through natural language queries.5MIT
- FlicenseAqualityDmaintenanceEnables natural-language queries about public GitHub repositories, including issues, pull requests, repo metadata, and READMEs, via the GitHub API.5-
- FlicenseNot gradedqualityCmaintenanceEnables hybrid and reranked semantic search across a repository's source code, documentation, and GitHub issues.-
- FlicenseNot gradedqualityDmaintenanceEnables natural language queries to search GitHub for trending repositories by topic, summarize project READMEs, and compare multiple repos to uncover ecosystem patterns.2-
- AlicenseBqualityCmaintenanceEnables querying GitHub repos and stats, and managing DEV.to articles (list, create, update) through natural language.7MIT
- AlicenseNot gradedqualityBmaintenanceEnables natural language search and querying of your GitHub starred repositories.7 npm116Apache 2.0
TDQS
Scored across 3 tools
Each tool has a distinct purpose, but search_repos and list_repos both return repository names and descriptions, with the only difference being keyword filtering. This overlap is manageable but could cause minor selection confusion.
All tool names follow a consistent verb_noun pattern with snake_case: search_repos, get_readme, list_repos. The naming convention is uniform and predictable.
With only 3 tools, the set is tightly scoped to a portfolio viewing purpose. Each tool is essential and there is no clutter or redundancy.
For a read-only portfolio server, the tools cover the core workflows: listing all repositories, searching by keyword, and retrieving a README. No critical operations are missing given the stated purpose.