Aedile
Click on "Deploy 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., "@Aedile check for existing date formatting utility before writing new code"
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.
Claude Code
│
▼
"Build authentication"
│
▼
Aedile MCP
┌────────────────────┐
│ Existing helper? │
│ Stdlib available? │
│ Import cycles? │
│ Layer violation? │
└────────────────────┘
│
▼
Minimal implementationWhy Aedile?
Modern coding assistants know how to write code. They usually don't know your architecture.
That leads to:
duplicate utilities
unnecessary dependencies
circular imports
broken layering
inconsistent implementations
Aedile verifies the repository before code generation begins, giving coding assistants real project context instead of relying solely on prompts.
Related MCP server: Manifold Engine MCP Server
Quick Example
Without Aedile
AI: "I'll install requests."
↓
Repository already has httpx.
↓
Duplicate dependency.With Aedile
AI: "Repository already uses httpx."
↓
Reuse existing client.
↓
No duplicate dependency.How It Works
Aedile implements the Model Context Protocol (MCP). The assistant calls a single tool—aedile_consult—before generating any code.
Developer
│
▼
Claude
│
▼
Aedile MCP
│
├── Architecture Verifier
├── Workspace Index
└── Decision Engine
│
▼
Advice
│
▼
Claude
│
▼
ImplementationAedile never modifies your code. It only observes and advises.
Installation
pip install aedileGenerate the local prompt templates:
python -m aedile compile-rulesThen add python -m aedile as an MCP server in your coding assistant. See SUPPORTED_AGENTS.md for step-by-step guides.
Configuration
Aedile works out of the box with zero configuration. Advanced options are documented in CONFIGURATION.md.
Supported Agents
Agent | Status |
Claude Code | ✓ Supported |
Cursor | ✓ Supported |
Windsurf | ✓ Supported |
Continue | ✓ Supported |
Full setup guides are in SUPPORTED_AGENTS.md.
Benchmarks
Benchmarks were measured using identical prompts on the same repository, before and after enabling Aedile.
Environment
Hardware: Apple M2 Pro, 16 GB RAM
Python: 3.11
Agent: Claude 2.1
Repository: 42 modules, ~8,000 lines of Python
Results
Metric | Without Aedile | With Aedile |
Reasoning Cost (avg tokens) | 1,850 | 350 |
Context Window (tokens) | 4,200 | 1,200 |
Duplicate Code Written | Yes | No |
Tool Calls Executed | 3 | 1 |
Full methodology and raw data: BENCHMARKS.md.
FAQ
Why not use static prompting (e.g., .cursorrules)?
Static prompts drift. As the context window fills, the model's adherence to static text degrades. Aedile enforces constraints through a live tool interface—the model receives current repository facts on every call, not instructions it may ignore.
Does Aedile require internet access?
No. All scanning, indexing, and analysis runs locally. There is no outbound network traffic and no telemetry.
Documentation
Contributing
Contributions are welcome. Please read CONTRIBUTING.md and CODE_OF_CONDUCT.md before opening a pull request.
License
Aedile is released under the MIT License.
Available Tools
1 toolaedile_consultA
Consult Aedile before implementing. Returns codebase symbol matches, stdlib alternatives, dependency reuse options, and checks proposed imports for cycles or layering violations.
Inputs: proposed_plan (required), proposed_changes.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
Only one tool exists, so there is no ambiguity. The agent cannot confuse it with other tools.
With a single tool, the naming pattern is perfectly consistent. 'aedile_consult' follows a descriptive noun_verb pattern.
A single tool is too few for effective agent workflow. The server's purpose (code consultation) would benefit from additional tools for actions like implementing suggestions.
The lone tool tries to cover multiple consultation aspects (symbols, stdlib, dependencies, imports), but the absence of any action tools leaves obvious gaps in the implementation workflow.
Maintenance
Related MCP Connectors
Code intelligence platform for AI agents. 20 tools for architecture, security & impact analysis.
Codebase intelligence for AI agents — dead code, blast radius, ownership.
Enforces architectural invariants and code quality rules inside your AI agent's edit loop.
AI Agent with Architectural Memory. Impact analysis (free), tests and code from the graph (pro).
Related MCP Servers
- AlicenseAqualityBmaintenanceSelf-hosted semantic code search for AI coding agents. Indexes many repositories at once with tree-sitter AST chunking, local llama.cpp embeddings and Qdrant, so Claude Code, Cursor, Codex and any MCP client can find code by meaning, trace usages and callers, and read the git history behind each chunk. No API keys, and your code never leaves your machine.21834MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI coding assistants to perform high-speed structural codebase analysis and dynamic context management by mapping repositories as byte-streams and detecting architectural chaos.MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to analyze a local codebase and answer impact questions like 'what breaks if I change Y?' through local indexing, search, and reverse dependency analysis, with no code leaving the machine.425 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to retrieve precise, real-time architectural context—such as domains, models, routes, and events—from a codebase, avoiding the need to dump entire files into prompts.110 npm1MIT