github-directory-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | GitHub personal access token for higher rate limits and access to private repos. Generate at github.com → Settings → Developer settings → Personal access tokens. Fine-grained, read-only 'Contents' + 'Metadata' repo permissions are sufficient. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_github_directoriesA | Lists directories (folders) inside a GitHub repository at a given path. Set recursive=true to list every subdirectory in the repo instead of just the immediate children. |
| list_github_repositoriesA | Lists repositories for a GitHub user or organization. If 'owner' is omitted, lists repositories for the authenticated user (requires GITHUB_TOKEN env var). |
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 2 tools
Each tool targets a distinct resource: one lists directories within a repository, the other lists repositories for a user/org. No overlap in purpose.
Both tools follow a consistent 'list_github_<plural>' pattern, using snake_case and similar structure.
With only 2 tools, the server feels thin for a GitHub utility. It may be intentionally scoped, but the count is borderline low.
The server only covers listing of directories and repositories, missing essential operations like file content access, creation, update, or deletion for either resource.