
Silex
io.github.silex-tecPublished by GitHub account silex-tecv0.11.38Updated Oct 24, 2026
Local-first MCP server that reconstructs architecture, workflows and business rules from your code.
Overview
Silex is a local MCP server that reconstructs a codebase's architecture, dependencies, workflows and business rules and serves that understanding to AI coding.
- What you can do
- Scan a local codebase across languages such as C#, JS/TS, Java, PHP, COBOL and VB to recover its architecture and dependencies. Map the system's communities and classify vendor or generated code out of the way. Surface workflows and business rules, with each claim anchored to a file and line and a verified quote. Flag unknown territory where nothing can be proven instead of guessing. Produce a shareable evidence report.
- When to use it
- Useful when an assistant must understand an unfamiliar or legacy codebase before changing it, and you want findings backed by file-and-line evidence rather than inference. Suited to local, privacy-sensitive work where code should not leave the machine.
- Requirements
- Runs as a local stdio process on the desktop. Needs Python 3.10 or later and the silex-archaeology package installed from PyPI (or a release wheel), then configured in an MCP client with the silex-mcp-server command and serve --stdio arguments. No account, card or API key is required.
Installation
In SourceWeft
- Open Silex in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Silex — evidence-based code archaeology
Understand the codebase before changing the code.
Silex reconstructs architecture, dependencies, workflows and business rules
from your source code — and serves that understanding to your AI coding
agents via MCP. Every claim is anchored to
file:line with a verified quote. What Silex can't prove, it tells you.
Local-first. Your code never leaves your machine. No account, no card, no telemetry.
→ Site & docs: https://silex.tec.br · Concepts · MCP tool reference · llms.txt
Install (free tier)
Until the PyPI release lands you can install the wheel from Releases:
pip install https://github.com/silex-tec/silex/releases/latest/download/silex_archaeology-py3-none-any.whl
Connect it to your MCP client (Claude Code, Cursor, Claude Desktop, Windsurf, Cline, Continue, Zed) — stdio config:
Full install guide (Windows/PowerShell notes included): https://silex.tec.br/docs/
Try it on a real codebase
Clone Microsoft's eShop (MIT) and point a scan at it — the Concepts page shows the community graph, the recovered order state machine and anchored findings from that exact scan, so you can compare your output against a published reference.
What you get (free)
- Local MCP server, full codebase scan (C#, JS/TS, Java, PHP, COBOL, VB…)
- Community map — the real shape of the system, vendor/generated classified out of the way by default
- Evidence anchored to
file:line, confidence with provenance - Unknown-territory detection: what can't be proven is flagged, not guessed
- Shareable evidence report
- Works with the AI seat you already pay for
Pro tier (team workspaces, deep architecture visualization, refactoring trust contracts): coming soon — join the waitlist.
Issues & feedback
Bug reports and field feedback are welcome in Issues. The engine is proprietary; this repository hosts distribution, documentation and the public roadmap conversation.
© 2026 SILEX. All rights reserved.
Source: README.md at commit 082fe14
Tools
0Version history
1- v0.11.38LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts