repofit
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_evidenceA | Collect what the user's local coding agents know (installed tools, memory files and, at level L2, the user's own session messages), redacted and numbered, with instructions for writing a profile. Long results come in parts. |
| save_profileB | Save the profile JSON written from get_evidence. Refs that do not exist are dropped. Returns the profile and the instructions for the search expansion. |
| save_expansionC | Save the search terms and project names written for each profile entry. |
| show_profileA | Show the saved profile. |
| find_candidatesB | Retrieve candidate GitHub repositories for the profile and return them with ranking instructions. Long results come in parts. |
| save_recommendationsA | Save the ranking JSON written from find_candidates. Picks that name unknown candidates or profile entries are dropped. Returns the recommendations to show the user. |
| show_recommendationsB | Show the last saved recommendations. |
| check_repoA | Judge whether one GitHub repository fits the user: its facts, whether they already use it, and which profile entries it matches. Looks the repo up on GitHub if it is not indexed. |
| search_reposA | Keyword search over the indexed GitHub repositories, leaving out what the user already uses. |
| unused_toolsA | List installed MCP servers and skills that no session ever called. |
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 10 tools
The tools mostly represent distinct pipeline stages: evidence collection, profile saving/showing, candidate finding, recommendation saving/showing, repo checking, and repo searching. The closest overlap is between find_candidates, search_repos, and check_repo, but their descriptions distinguish profile-based retrieval, keyword search, and single-repo judgment.
Most names follow a clear verb_noun snake_case pattern such as save_profile, find_candidates, and show_recommendations. The only notable deviation is unused_tools, which is a noun phrase rather than an action verb.
Ten tools is well within a reasonable scope for a multi-step profile-to-recommendation workflow. Each tool appears to serve a specific step in that flow, with search and check helpers adding useful coverage.
The surface covers the core lifecycle: collecting evidence, saving/showing a profile, expanding searches, finding candidates, saving/showing recommendations, and checking or searching repositories. Minor gaps exist around deleting or resetting saved profiles/recommendations and explicitly viewing saved expansions.