developer-presence-mcp
Related Servers
Alternatives to developer-presence-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables interaction with GitHub API for repository management, commits, pushes, and pulls through natural language.256 npm1ISC
- AlicenseNot gradedqualityDmaintenanceEnables interacting with GitHub repositories for pull requests, code, and reviews through natural language.MIT
- FlicenseAqualityBmaintenanceEnables searching and retrieving GitHub portfolio repositories and their READMEs through natural language.3-
- FlicenseNot gradedqualityCmaintenanceEnables querying today's GitHub commits, performing local git operations (status, diff, add, commit, push), and creating GitHub issues through natural language.-
- FlicenseAqualityDmaintenanceEnables natural-language queries about public GitHub repositories, including issues, pull requests, repo metadata, and READMEs, via the GitHub API.5-
- 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-
TDQS
Scored across 7 tools
Each tool targets a distinct entity or action: repos, articles, and profile. list_repos and get_repo_stats are clearly separate (list vs stats), and article tools cover create, update, list, and stats without ambiguity.
All tools follow a consistent verb_noun pattern with lowercase and underscores (e.g., list_articles, create_article, get_repo_stats). The naming is predictable and clear.
7 tools cover two logical domains (GitHub repos and DEV.to articles) without being too many or too few. Each tool serves a distinct purpose within the scope of developer presence.
The tool set covers basic operations for articles (list, create, update, stats) but lacks delete. For repos, only list and stats are available; missing individual repo details. Minor gaps affect core workflows.