Schema | Repo Therapist

Repo Therapist

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{}

Functions exposed to the LLM to take actions

Name	Description
analyze_repoA	Analyze a repository to understand its structure, dependencies, and git history. Run this first before asking questions.
ask_repoC	Ask a question about an analyzed repository. Questions can be about structure, purpose, dependencies, patterns, or concerns.
repo_summaryB	Get a high-level summary of the analyzed repository including tech stack, structure, and key components.
risk_reportC	Generate a risk assessment report identifying code smells, complexity hotspots, and areas that might cause problems.
get_snapshotA	Get the static snapshot (ground truth) of the repository. This is the authoritative source - LLMs must cite this data, not guess. Use section parameter to get specific data.
get_historyB	Get git history analysis - the time dimension. Reveals WHY code is the way it is: file churn, ownership, fragile files, hot paths vs stable core.
why_is_this_weirdA	Explain why a specific file is the way it is, based on git history. Answers questions like 'Why is this file so complex?' with data: 'Because it's been rewritten 12 times by 5 different people.'

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/salman-arefin74/repo-therapist'

If you have feedback or need assistance with the MCP directory API, please join our Discord server