Suitable Loop
Analyzes git repositories, scoring commits by risk (complexity delta × blast radius × churn × size) and identifying hotspots, providing tools for commit analysis and blast radius assessment.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Suitable Loopindex my codebase and give a summary"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Suitable Loop
Local production engineering platform — semantic code analysis, git risk scoring, and log correlation via MCP.
What it does
Suitable Loop indexes your Python codebase and exposes deep analysis through MCP tools that AI assistants can call:
Code Analysis — AST-based parsing, function/class extraction, call graph construction, cyclomatic complexity
Git Risk Scoring — Weighted risk scores per commit (complexity delta × blast radius × churn × size)
Log Correlation — Parse logs, group errors by signature, map stack frames to indexed code
Dependency Graph — NetworkX-powered call graphs, import trees, blast radius analysis
Related MCP server: SocratiCode
Quick Start
1. Add MCP server to your project
Create .mcp.json in your project root:
{
"mcpServers": {
"suitable-loop": {
"command": "uvx",
"args": ["suitable-loop"]
}
}
}That's it. uvx fetches the package from PyPI automatically — no manual install needed.
Local development? Point to a local checkout instead:
"args": ["--from", "/path/to/suitable-loop", "suitable-loop"]
2. Install slash commands (optional)
Clone the repo and copy the commands into your project:
git clone https://github.com/suitable-adventures/suitable-loop.git /tmp/suitable-loop
mkdir -p .claude/commands
cp /tmp/suitable-loop/.claude/commands/* .claude/commands/3. Restart Claude Code and start using it
/onboard # Get a full codebase orientation
/risk-report # Analyze recent commits by risk
/impact-check models.py # Check blast radius before changing a file
/debug-error "ConnectionResetError in db/pool.py"
/health-check # Full codebase health assessment
/trace-function my_function # Map a function's callers and calleesSlash Commands
Command | What it does |
| Index the codebase and produce a full orientation: structure, hotspots, complexity, blast radius |
| Score recent commits by risk, find hotspots, recommend where to focus review |
| Before changing a file: blast radius, who calls what, what could break |
| Correlate an error/traceback to source code paths |
| Full assessment: complexity, coupling, churn trends, actionable recommendations |
| Map a function's callers, callees, complexity, and role in the system |
| Bump version, tag, and publish a new release to PyPI |
MCP Tools
Code Analysis
Tool | Description |
| Index a Python project — parse AST, extract entities, build call graph |
| Look up a function/class/file by name with all relationships |
| Find all functions that call a given function |
| Find all functions called by a given function |
| Get import dependency tree for a file |
| Full-text search across indexed functions and classes |
| Top N most complex functions |
| High-level stats and most-connected modules |
Git Analysis
Tool | Description |
| Score recent commits by risk |
| Deep-dive a single commit |
| Files with high churn × high dependency count |
| Transitive impact of changing a file |
Log Analysis
Tool | Description |
| Parse log files, extract errors, group by signature |
| List distinct error groups by frequency |
| Full detail on an error group with code links |
| Map raw error text to code paths |
| Error frequency over time |
Utility
Tool | Description |
| Server status and entity counts |
| Incremental re-index (only changed files) |
Architecture
suitable_loop/
├── __init__.py # Package root
├── __main__.py # Entry point (python -m suitable_loop)
├── server.py # MCP server setup (FastMCP) + main() entry point
├── config.py # Configuration dataclasses
├── models.py # Data models (entities, edges)
├── db.py # SQLite database layer
├── analyzers/
│ ├── code_analyzer.py # AST parsing, call resolution
│ ├── git_analyzer.py # Commit analysis, risk scoring
│ └── log_analyzer.py # Log parsing, error grouping
├── graph/
│ └── engine.py # NetworkX graph engine
└── tools/
├── code_tools.py # MCP code analysis tools
├── git_tools.py # MCP git analysis tools
├── log_tools.py # MCP log analysis tools
└── util_tools.py # MCP utility toolsConfiguration
Environment variables:
Variable | Default | Description |
|
| SQLite database path |
|
| Logging level |
Default exclude patterns (files skipped during indexing):
.venv/,venv/,node_modules/,__pycache__/,migrations/,.git/
Development
For working on Suitable Loop itself:
cd suitable-loop
uv venv && uv pip install -e ".[dev]"
uv run pytestMaintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/suitable-adventures/suitable-loop'
If you have feedback or need assistance with the MCP directory API, please join our Discord server