engineering-server
MCP Server for Universal Engineering Workflow - AI-Assisted Development
Installation
npx mcp-engineering-serverAsk AI about engineering-server
Powered by Claude Β· Grounded in docs
I know everything about engineering-server. Ask me about installation, configuration, usage, or troubleshooting.
0/500
Reviews
Documentation
MCP Engineering Server (ARCHIVE CUZ ANTHROPIC JUST COPY ALL MY INTERLECTUAL PROPERTY THEIR /COMMAND JUST PRETTY MUCH STOLEN ALL MY THINKING PARTTERN LOOK AT THEIR NEW RELEASE AND COMPARE IT IDEA WITH THIS REPO TIMELINE YOU WILL UNDERSTAND HOW BULLSHIT IT IS FOR ANTHROPIC TO STOLEN MY IDEA)
An MCP (Model Context Protocol) server and Claude Code plugin for AI-assisted engineering workflows.
Features
- Auto-detect project type: Supports 20+ project types (Node.js, .NET, Python, Rust, Go, Embedded, etc.)
- Security scanning: Detect secrets, API keys, and credentials before commit
- Function indexing: Index and search functions across TypeScript, Python, C#, Go, Rust, C/C++
- Duplicate detection: Find duplicate code blocks for refactoring
- Route indexing: Index API routes (Express, Flask, FastAPI, ASP.NET, Go)
- Hardware indexing: Index embedded hardware configs (STM32, ESP32, Arduino)
- Knowledge base: Extract and query learnings from completed features
- Session management: Checkpoints for context preservation across Claude sessions
- Multi-session coordination: Parallel Claude instances with file locking
Installation
Quick Install (Recommended)
npm install -g mcp-engineering-server
mcp-engineering-server install
That's it! The install command will:
- Copy slash commands to
~/.claude/commands/(global) - Register the MCP server with Claude Code
From Source
git clone https://github.com/liam1472/mcp-engineering-server.git
cd mcp-engineering-server
npm install && npm run build
# Install globally
npm link
mcp-engineering-server install
Uninstall
mcp-engineering-server uninstall
npm uninstall -g mcp-engineering-server
Slash Commands
Core Workflow
| Command | Description |
|---|---|
/eng-init | Initialize project, auto-detect type |
/eng-scan | Build function index |
/eng-security | Scan for secrets and credentials |
/eng-security --fix | Auto-fix: create .env, replace secrets, backup files |
/eng-security --fix --dry-run | Preview what --fix would change |
/eng-start <feature> | Start working on a feature |
/eng-validate | Run validation pipeline |
/eng-done | Complete and archive feature |
/eng-search <query> | Search indexed functions |
Analysis & Refactoring
| Command | Description |
|---|---|
/eng-refactor | Analyze code for refactoring opportunities |
/eng-refactor --fix | Auto-fix: add constants, backup files |
/eng-refactor --fix --dry-run | Preview what --fix would change |
/eng-review | Pre-completion checklist (security, build, tests) |
/eng-deps | Analyze dependencies, detect circular imports |
/eng-pipeline | Run full validation pipeline (build, lint, test) |
/eng-duplicates | Detect duplicate code blocks |
Indexing
| Command | Description |
|---|---|
/eng-index-function [query] | Search indexed functions |
/eng-index-similar <code> | Find similar code snippets |
/eng-routes | Index API routes (web projects) |
/eng-hardware | Index hardware configs (embedded) |
/eng-knowledge [query] | Query knowledge base |
Session Management
| Command | Description |
|---|---|
/eng-checkpoint | Save session checkpoint |
/eng-resume | Resume from checkpoint |
/eng-session-start <A|B|C> | Start parallel session |
/eng-session-status | View active sessions |
/eng-session-switch <A|B|C> | Switch between sessions |
/eng-session-sync | Sync discoveries between sessions |
/eng-lock <file> | Lock file for editing |
/eng-unlock <file> | Unlock file |
Workflows & Scenarios
Scenario 1: New Project Setup
First time using the plugin on a project:
/eng-init # Auto-detect project type, create .engineering/
/eng-scan # Index all functions in codebase
/eng-security # Check for any existing secrets/credentials
What happens:
.engineering/directory created with config- Project type detected (e.g.,
web-node,embedded-stm32,python-fastapi) - Function index built at
.engineering/index/functions.yaml - Security report generated
Scenario 2: Feature Development (Standard Flow)
Working on a new feature from start to finish:
# 1. Start feature - creates context directory
/eng-start user-authentication
# 2. Work on your code...
# Claude assists with implementation
# 3. Before committing - validate everything
/eng-validate # Runs: security scan + index update + status check
# 4. If security issues found
/eng-security --fix # Auto-create .env, replace hardcoded secrets
# 5. Complete feature - archives context, extracts knowledge
/eng-done
What happens:
- Feature directory created at
.engineering/features/user-authentication/ - Progress tracked in
progress.yaml - On
/eng-done: archived to.engineering/archive/, learnings extracted to knowledge base
Scenario 3: Security Audit
Find and fix secrets before pushing to git:
# Scan for secrets
/eng-security
# Preview what auto-fix would do (safe, no changes)
/eng-security --fix --dry-run
# Apply fixes: create .env, replace secrets in code, backup originals
/eng-security --fix
Example output:
Security Scan Results:
CRITICAL: 2 findings
- src/config.ts:15 - Hardcoded API key (OPENAI_API_KEY)
- src/db.ts:8 - Database password in connection string
Run `/eng-security --fix` to auto-remediate
Scenario 4: Code Analysis & Refactoring
Find code quality issues:
# Find magic numbers, duplicate code, refactoring opportunities
/eng-refactor
# Preview auto-fix
/eng-refactor --fix --dry-run
# Apply fixes: extract constants, add config files
/eng-refactor --fix
# Find duplicate code blocks
/eng-duplicates
# Analyze dependencies, find circular imports
/eng-deps
Scenario 5: Search & Discovery
Find code in large codebases:
# Search functions by name or description
/eng-search "authentication"
/eng-search "parse JSON"
# Find similar code blocks (for refactoring)
/eng-index-similar "function validateUser(email, password)"
# Query knowledge base from past features
/eng-knowledge "how did we handle rate limiting"
# Index and search API routes (web projects)
/eng-routes
# Index hardware peripherals (embedded projects)
/eng-hardware
Scenario 6: Session Management
Preserve context across Claude sessions:
# Save checkpoint before ending session
/eng-checkpoint
# ... close Claude, come back later ...
# Resume from checkpoint (restores context)
/eng-resume
Scenario 7: Parallel Development (Multi-Session)
Multiple Claude instances working on same codebase:
# Terminal 1: Start session A
/eng-session-start A
/eng-lock src/auth/login.ts # Lock file to prevent conflicts
# Terminal 2: Start session B
/eng-session-start B
/eng-lock src/auth/register.ts # Lock different file
# Check all sessions and locks
/eng-session-status
# Sync discoveries between sessions
/eng-session-sync
# When done, unlock files
/eng-unlock src/auth/login.ts
Session status output:
Active Sessions:
A: Working on src/auth/login.ts (locked)
B: Working on src/auth/register.ts (locked)
C: Inactive
Locked Files:
- src/auth/login.ts (Session A)
- src/auth/register.ts (Session B)
Scenario 8: Pre-Commit Review
Final checks before creating PR:
# Run full validation pipeline
/eng-pipeline # build + lint + test + security
# Or run review checklist
/eng-review # Shows: security status, test status, build status
Review output:
Pre-Completion Review:
[x] Security scan passed
[x] Build successful
[x] Tests passing (48/48)
[ ] Lint warnings: 3
Recommendation: Fix lint warnings, then ready for /eng-done
Quick Reference
| Goal | Command |
|---|---|
| Setup new project | /eng-init β /eng-scan |
| Start feature | /eng-start <name> |
| Find secrets | /eng-security |
| Fix secrets | /eng-security --fix |
| Search code | /eng-search <query> |
| Find duplicates | /eng-duplicates |
| Check dependencies | /eng-deps |
| Save progress | /eng-checkpoint |
| Resume work | /eng-resume |
| Final validation | /eng-validate or /eng-pipeline |
| Complete feature | /eng-done |
Generated Structure
After running /eng-init, a .engineering/ directory is created:
.engineering/
βββ config.yaml # Project config
βββ index/
β βββ functions.yaml # Function index
β βββ routes.yaml # API routes (web)
β βββ hardware.yaml # Hardware configs (embedded)
β βββ duplicates.yaml # Duplicate code report
βββ sessions/ # Session data (gitignore this)
βββ security/
β βββ patterns.yaml # Detection patterns
β βββ whitelist.yaml # False positive whitelist
βββ knowledge/
β βββ base.yaml # Extracted learnings
βββ features/ # Active features
βββ archive/ # Completed features
Supported Project Types
| Type | Detection |
|---|---|
web-node | package.json |
web-react | package.json + react |
web-vue | package.json + vue |
web-angular | angular.json |
dotnet-aspnet | *.csproj + ASP.NET |
dotnet-maui | *.csproj + MAUI |
python-django | manage.py |
python-fastapi | main.py + fastapi |
rust | Cargo.toml |
go | go.mod |
embedded-stm32 | *.ioc |
embedded-esp | sdkconfig |
mobile-flutter | pubspec.yaml |
mobile-react-native | react-native in package.json |
Security Patterns
The security scanner detects:
- AWS Access Keys & Secret Keys
- GCP API Keys
- Azure Storage Keys
- OpenAI / Anthropic API Keys
- JWT Tokens
- Database connection strings (MongoDB, PostgreSQL, MySQL)
- RSA/SSH Private Keys
- Hardcoded passwords
Requirements
- Node.js >= 18.0.0
- Claude Code (VS Code extension or CLI)
License
MIT
