AI Code Surgeon: Think → Edit → Verify → Commit
The only MCP that combines reasoning, surgical diffs, syntax validation, and git commits in one workflow.
Traditional AI code editing: Copy → Paste → Format → Lint → Git commit → 10 minutes wasted.
mcp-coding-thinker: "Fix dark mode" → 90 seconds → ✅ Committed with perfect style.
- Analyze: Learns your code style (quotes, indentation, patterns)
- Think: Records reasoning steps for transparency
- Plan: Creates surgical line-by-line diffs with fuzzy matching
- Verify: Validates syntax, checks for conflicts, generates lintable preview
- Execute: Applies changes, auto-formats with Prettier, backs up originals, commits to git
Most AI code tools either just suggest changes OR execute them. This does both with full reasoning transparency:
- Code-aware thinking: Records WHY each change is made, not just WHAT
- Surgical precision: Line-by-line diffs with overlap handling, not full-file replacements
- Zero manual work: Auto-formats + syntax checks + git commits in one flow
- Always safe: Backups every file, validates before writing, handles git edge cases
- Style-aware: Learns your existing code patterns and enforces them automatically
claude mcp add coding-thinker -- npx -y mcp-coding-thinkergemini mcp add coding-thinker npx -y mcp-coding-thinkerEdit ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"coding-thinker": {
"command": "npx",
"args": ["-y", "mcp-coding-thinker"]
}
}
}Edit %APPDATA%\Claude\claude_desktop_config.json:
{
"mcpServers": {
"coding-thinker": {
"command": "npx",
"args": ["-y", "mcp-coding-thinker"]
}
}
}Edit ~/.config/Claude/claude_desktop_config.json:
{
"mcpServers": {
"coding-thinker": {
"command": "npx",
"args": ["-y", "mcp-coding-thinker"]
}
}
}Restart Claude Desktop after saving.
Create/edit MCP config file (location varies by OS):
- macOS/Linux:
~/.config/gemini/mcp_config.json - Windows:
%APPDATA%\Gemini\mcp_config.json
{
"mcpServers": {
"coding-thinker": {
"command": "npx",
"args": ["-y", "mcp-coding-thinker"]
}
}
}# Start the server with npx
npx -y mcp-coding-thinker
# Or test with MCP Inspector
npx @modelcontextprotocol/inspector npx -y mcp-coding-thinkerPrompt to AI (Claude/Gemini):
Use coding-thinker to fix the dark mode color contrast in Header.tsx
What Happens:
- Analyzes
Header.tsx→ Detects React + Tailwind + 2-space indent - Records thoughts: "Dark text on dark bg detected at line 42"
- Creates diff: Change
text-gray-900→text-gray-100 - Validates syntax ✅
- Formats with Prettier ✅
- Backs up to
.mcp-backups/✅ - Commits:
"mcp-coding-thinker: Fix dark mode contrast"✅
Result: Production-ready commit in 90 seconds.
- Input: Files + request
- Output: Session ID, style profile, issues, research queries
- Use: Always call first
- Input: Session ID + reasoning step
- Output: Recorded thought + depth score
- Use: Show incremental reasoning (5+ steps = excellent quality)
- Input: Session ID + diffs (line-by-line changes)
- Output: Validation results, safety score, lintable preview
- Use: Submit exact diffs for verification
- Input: Session ID + approval
- Output: Execution status, git operations, mirror critique prompt
- Use: Apply changes with full safety net
- ✅ Detects detached HEAD, rebase/merge in progress
- ✅ Handles pre-commit hook failures gracefully
- ✅ Provides revert instructions:
git revert HEAD
- ✅ Copies originals to
.mcp-backups/{session-id}/ - ✅ Preserves directory structure
- ✅ 1-hour session TTL (auto-cleanup)
- ✅ Syntax check before formatting (no silent fails)
- ✅ Fuzzy diff matching (±2 lines tolerance)
- ✅ Overlapping diff detection with unified patching
- ✅ 80% similarity threshold for stale diffs
- ✅ Size limits on diffs (prevents memory issues)
- ✅ Cross-platform line ending normalization (CRLF/LF)
- ✅ Prettier config detection from user's repo
- Always analyze first: Call
analyze_contextbefore planning - Think deeply: 5+
think_aloudcalls = 95%+ confidence - Exact diffs: Provide real line numbers from original files
- Dry run first: Use
dry_run=trueto preview before executing
- Commit changes before using (or work on feature branch)
- Review mirror critique prompt for architectural insights
- Use research queries to verify best practices
- Check
.mcp-backups/if rollback needed
git clone https://github.com/awssat/mcp-coding-thinker.git
cd mcp-coding-thinker
npm install
npm run build
# Test with MCP Inspector
npm run inspectorPRs welcome! Priority areas:
- Additional language support
- Test coverage
- Performance optimizations
MIT © 2026