github-portfolio-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_reposA | 내 GitHub 계정의 모든 공개 레포 목록을 이름과 설명과 함께 가져옵니다. |
| search_reposA | 키워드로 내 레포 이름과 설명을 검색합니다. |
| get_readmeA | 특정 레포의 README 내용을 가져옵니다. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.