MCP-Repo2LLM
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | Your GitHub token for accessing GitHub repositories | |
| GITLAB_TOKEN | No | Your GitLab token for accessing GitLab repositories |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_gitlab_repoC | Process and return the code from a GitLab repository branch as text |
| get_github_repoC | Process and return the code from a GitHub repository branch as text |
| get_local_repoC | Process and return the code from a local repository as text |
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 clearly distinct purpose targeting a different repository source: GitHub, GitLab, and local repositories. The descriptions explicitly differentiate them by source, leaving no ambiguity about which tool to use for each scenario.
All tools follow a consistent verb_noun pattern with 'get_' prefix and descriptive suffixes indicating the repository source. The naming is uniform and predictable across all three tools.
With only 3 tools, the server feels thin for its apparent scope of repository code retrieval. While it covers three repository sources, the functionality is limited to a single 'get' operation without supporting related actions like searching, filtering, or managing repositories.
The tool surface is severely incomplete for repository interaction. It only provides retrieval operations without any create, update, delete, search, or management capabilities. Even within retrieval, there are no options for filtering, pagination, or handling different file types beyond returning 'code as text'.