Engineering Intelligence
БесплатноНе проверенEnables AI clients to inspect backend systems through structured engineering tools including Git history, Winston logs, OpenAPI contracts, and sandboxed source
Описание
Enables AI clients to inspect backend systems through structured engineering tools including Git history, Winston logs, OpenAPI contracts, and sandboxed source code.
README
A production-oriented Model Context Protocol (MCP) server for Express.js applications that enables AI clients to inspect backend systems through structured engineering tools instead of direct file system access.
The server exposes backend engineering context including Git history, Winston logs, OpenAPI/Swagger contracts, and sandboxed source code through MCP tools. The implementation has been validated using both the official MCP Inspector and Claude Desktop.
Features
- MCP-compliant server using the official MCP SDK
- Tool Registry based architecture
- Git history provider
- Winston log provider
- Dynamic Swagger/OpenAPI provider
- Sandboxed source code provider
- Compatible with Claude Desktop
- Validated using the official MCP Inspector
- Extensible provider architecture
- Read-only engineering context
Architecture
flowchart TD
Client[Claude Desktop / MCP Inspector]
Transport[STDIO Transport]
Server[MCP Server]
Registry[Tool Registry]
Git[Git Provider]
Swagger[Swagger Provider]
Logs[Winston Provider]
Source[Source Code Provider]
Express[(Express Application)]
Client <--> Transport
Transport <--> Server
Server --> Registry
Registry --> Git
Registry --> Swagger
Registry --> Logs
Registry --> Source
Git --> Express
Swagger --> Express
Logs --> Express
Source --> Express
Provider Responsibilities
| Provider | Responsibility |
|---|---|
| Git Provider | Reads Git commit history for project files |
| Swagger Provider | Reads dynamically generated OpenAPI contracts |
| Log Provider | Retrieves Winston application logs |
| Source Provider | Lists directories and securely reads project source code |
| Tool Registry | Registers and dispatches MCP tool requests |
Tech Stack
| Category | Technology |
|---|---|
| Runtime | Node.js |
| Framework | Express.js |
| Protocol | Model Context Protocol |
| Logging | Winston |
| API Documentation | Swagger JSDoc |
| Database | MySQL + Sequelize |
| Version Control | Git |
| AI Client | Claude Desktop |
| Testing | MCP Inspector |
Installation
git clone <repository>
npm install
npm run dev
Configure Claude Desktop:
{
"mcpServers": {
"engineering-intelligence": {
"command": "node",
"args": [
"/absolute/path/mcp/server.js"
]
}
}
}
Restart Claude Desktop.
Available MCP Tools
| Tool | Description |
|---|---|
| check_file_history | Returns recent Git history for a file |
| read_winston_logs | Reads recent Winston logs |
| analyze_api_contract | Reads OpenAPI contract for an endpoint |
| list_directory | Lists project directories |
| read_source_code | Reads project source files securely |
Working Example
Prompt
Compare the implementation of POST /orders with its OpenAPI contract.
Tool Execution
| Phase | Tool |
|---|---|
| API Contract Inspection | analyze_api_contract |
| Source Inspection | read_source_code |
| Analysis | Claude Desktop |
Result
The server successfully detected a contract mismatch between the documented API and the controller implementation.
Example:
- Swagger contract expects customerId
- Controller consumes userId
This demonstrates how multiple MCP tools can be orchestrated by an AI client to investigate backend implementation issues.
Testing
The implementation was validated using two independent MCP clients.
MCP Inspector
- Tool discovery
- Tool execution
- Protocol validation
- Response verification
Claude Desktop
Successfully connected without code changes.
Validated:
- Git history inspection
- Winston log retrieval
- Swagger analysis
- Source code inspection
This confirms interoperability with real MCP clients.
Project Structure
project/
├── app.js
├── index.js
├── logger.js
├── swaggerConfig.js
├── controllers/
├── models/
├── routes/
├── validations/
├── config/
├── mcp/
│ ├── server.js
│ ├── registry/
│ │ └── toolRegistry.js
│ └── providers/
│ ├── gitProvider.js
│ ├── logProvider.js
│ ├── swaggerProvider.js
│ └── sourceCodeProvider.js
└── package.json
Roadmap
- AST-based source code analysis
- Sequelize schema provider
- Express route dependency graph
- Architecture summarization
- Middleware analysis
- Configuration provider
- Project dependency analysis
License
Licensed under the ISC License.
Установка Engineering Intelligence
У этого сервера нет опубликованного пакета — он собирается из исходников. Открой репозиторий и следуй инструкции в README.
▸ github.com/sanchit0496/engineering-intelligence-mcpFAQ
Engineering Intelligence MCP бесплатный?
Да, Engineering Intelligence MCP бесплатный — установка в пару кликов через Unyly без оплаты.
Нужен ли API-ключ для Engineering Intelligence?
Нет, Engineering Intelligence работает без API-ключей и переменных окружения.
Engineering Intelligence — hosted или self-hosted?
Self-hosted: сервер запускается локально на твоей машине командой из раздела установки.
Как установить Engineering Intelligence в Claude Desktop, Claude Code или Cursor?
Открой Engineering Intelligence на unyly.org, выбери вкладку своего клиента (Claude Desktop, Claude Code, Cursor) и нажми Install — конфиг сгенерируется автоматически, без правки JSON.
Похожие MCP
GitHub
PRs, issues, code search, CI status
автор: GitHubFilesystem
Secure file operations with configurable access controls.
Memory
Knowledge graph-based persistent memory system.
Template MCP Server
A CLI tool to create a new Model Context Protocol server project with TypeScript support, dual transport options, and an extensible structure
автор: mcpdotdirectCompare Engineering Intelligence with
Не уверен что выбрать?
Найди свой стек за 60 секунд
Автор?
Embed-бейдж для README
Похожее
Все в категории development
