Sacl MCP Server

SACL (Semantic-Augmented Reranking and Localization) MCP Server for bias-aware code retrieval. Exposed over MCP by the sacl mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

A Model Context Protocol (MCP) server that implements the SACL research framework to provide bias-aware code retrieval for AI coding assistants like Claude Code, Cursor, and other MCP-enabled tools.

• 🧠 Bias Detection — Identifies over-reliance on textual features
• 🔍 Semantic Augmentation — Enriches code understanding beyond surface text
• 📊 Intelligent Reranking — Prioritizes functional relevance over documentation
• 🎯 Code Localization — Pinpoints functionally relevant code segments
• 🔗 Relationship Analysis — Maps code dependencies and relationships
• 🎨 Context-Aware Retrieval — Returns results with related components

Its toolset

Everything the assistant can do here goes through one of these:

• Cursor — MCP server connection
• Prerequisites — The Prerequisites tool exposed by this server
• Installation — The Installation tool exposed by this server
• Building — The Building tool exposed by this server
• Contributing — 1. Fork the repository 2. Create a feature branch 3. Implement changes following SACL methodology 4. Add tests for new functionality 5. Submit a pull

Configuration

You will need 5 environment variables: OPENAI_API_KEY, NEO4J_URI, NEO4J_USER, NEO4J_PASSWORD, SACL_REPO_PATH. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js 18+ - Neo4j database - OpenAI API key

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Sacl's toolset — Cursor, Prerequisites, Installation and 2 more — is a fair guide to whether it matches your workflow. It is maintained by ulasbilgen; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Sacl's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the sacl mcp server does with a few real requests.