This server wraps Claude Sonnet 4.5 to provide a proactive thinking tool that analyzes problems before you write code. It exposes a single `claude_think` operation that takes context about errors, feature requests, architecture decisions, or performance issues and returns strategic insights and implementation guidance. You'd reach for this when you want Claude to reason through a problem first instead of jumping straight to code generation. Ships with Docker config and a `.cursorrules` file that trains Cursor IDE to automatically invoke the think tool when new information arrives. The workflow is simple: pass it an error message or requirement, get back analysis and recommendations, then write better code on the first attempt. Requires an Anthropic API key and runs as a streamable HTTP server on localhost:8080.
A powerful Model Context Protocol (MCP) server that provides proactive deep analytical thinking using Anthropic's Claude Sonnet 4.5. This tool is designed to be called BEFORE writing code when new information arrives.
Use this tool FIRST when new information arrives, BEFORE writing any code:
Workflow: New Info → Think Tool → Review Insights → Write Better Code
claude_think)Provides intelligent insights, suggestions, and strategic guidance before code implementation. Perfect for:
Result: Fewer bugs, better code quality, faster development!
cd claude-vision-mcp
bun install
# or
npm install
The API key is configured when connecting to the MCP server (see Docker or Cursor setup below).
bun run build
# or
npm run build
cd claude-vision-mcp
# Create .env file with your API key
echo "ANTHROPIC_API_KEY=your-key-here" > .env
echo "CLAUDE_MODEL=claude-sonnet-4-20250514" >> .env
# Start container
docker-compose up -d
# Check status
docker ps | grep claude-vision
The container will auto-restart when Docker Desktop launches.
The server runs on http://localhost:8080/mcp with the following environment variables:
ANTHROPIC_API_KEY - Your Claude API key (required)CLAUDE_MODEL - Model to use (default: claude-sonnet-4-20250514)Add to your ~/.cursor/mcp.json or .cursor/mcp.json:
{
"mcpServers": {
"Claude Deep Think": {
"url": "http://localhost:8080/mcp?apiKey=YOUR_API_KEY&model=claude-sonnet-4-5-20250929"
}
}
}
Copy the .cursorrules file from this repo to your project root. This makes Cursor AI automatically use the think tool before writing code.
# From your project directory
cp claude-vision-mcp/.cursorrules .cursorrules
Always use this pattern when new information arrives:
Use the claude_think tool to analyze: [NEW INFORMATION]
Context: [Current situation, tech stack, constraints]
Examples:
Error Message:
Use the claude_think tool to analyze:
Error: "TypeError: Cannot read property 'map' of undefined"
Context: React component rendering users from useState hook
New Feature:
Use the claude_think tool:
Requirement: Add dark mode toggle to header
Context: Next.js 14, need to check if ThemeContext exists
Performance Issue:
Use the claude_think tool:
Issue: Homepage renders 50+ times, parent causing all children to re-render
Context: useState for theme in Header, passed via props to 20+ children
Use the claude_think tool to analyze:
"I'm building a real-time chat application. Should I use WebSockets, SSE, or HTTP polling?"
Context: Need to support 100K concurrent users, prioritize ease of implementation
Expected Output: Comprehensive comparison with pros, cons, and recommendations
Use the claude_think tool to evaluate:
"What's the best way to structure a multi-tenant SaaS application?"
Context: PostgreSQL database, Node.js backend, 50-100 tenants expected
Use the claude_think tool:
"Review this approach to handling user sessions in a Next.js app"
Context: Using JWT tokens, storing in localStorage, concerned about security
claude-vision-mcp/
├── src/
│ └── index.ts # Main MCP server implementation
├── .smithery/
│ └── index.cjs # Built server (generated)
├── package.json # Dependencies and scripts
├── tsconfig.json # TypeScript configuration
├── smithery.yaml # Smithery deployment config
├── Dockerfile # Docker container definition
├── docker-compose.yml # Docker Compose configuration
└── README.md # This file
bun run build / npm run build - Compile TypeScriptbun run dev / npm run dev - Development server with hot reload.env files are ignored# Start container
docker-compose up -d
# View logs
docker logs claude-vision-mcp-server -f
# Restart container
docker-compose restart
# Stop container
docker-compose down
# Rebuild and restart
docker-compose up -d --build
Solutions:
docker ps | grep claude-visiondocker logs claude-vision-mcp-serverSolutions:
sk-ant-Solutions:
# Check logs
docker logs claude-vision-mcp-server
# Verify .env file
cat .env
# Rebuild from scratch
docker-compose down -v
docker-compose up -d --build
With Bun runtime:
1. User reports error
2. AI writes quick fix
3. Fix creates new bug
4. Multiple iterations needed
⏱️ Total: 30 minutes, 3 iterations
1. User reports error
2. AI analyzes with claude_think tool (20s)
3. AI writes comprehensive fix
4. Works correctly first time
⏱️ Total: 5 minutes, 1 iteration
Result: 6x faster, better quality, fewer bugs! 🎉
MIT
Contributions are welcome! Please feel free to submit a Pull Request.
For issues or questions:
com.mcparmory/google-search
io.github.pipeworx-io/brave-search
marcopesani/mcp-server-serper
brave/brave-search-mcp-server
com.mcparmory/google-search-console
acamolese/google-search-console-mcp