This MCP server exposes AI-powered development tools that integrate with Cursor through Windsurf. It provides capabilities such as Code Architect for planning coding tasks, Screenshot Buddy for UI design analysis, Code Review using git diffs, and Read File / Read Multiple Files for targeted data extraction. After starting the server, configure Windsurf to point to the built index.js entry so the MCP tools appear under Available Tools in the Cursor composer. The tools will be suggested by the agent when appropriate, and you can also invoke them explicitly by name or description in your prompts.

Prerequisites:

• Node.js (18+ recommended) installed on your machine
• npm or yarn
• Git (optional, for cloning)

Install and run locally:

1. Clone the repository (or download the source): git clone https://github.com/yeakub108-mcp-server/repo-name.git cd repo-name

2. Install dependencies: npm install

   or

   yarn install

3. Build the server: npm run build

4. Run the server (example): npm start

   or run the built entry directly if you prefer:

   node build/index.js

5. Configure Windsurf MCP in Cursor:

   • Open Windsurf > Chat > + Configure MCP
   • Add the following configuration (adjust path if needed): { "mcpServers": { "mcp-server": { "command": "node", "args": [ "build/index.js" ] } } }

6. Ensure your environment variables are set (example: OPENAI_API_KEY) either in a .env file or via Windsurf UI as needed.

Notes and tips:

• Security: Do not hard-code API keys in production. Use environment variables or a secrets manager.
• If you modify environment variables, restart the MCP server so changes take effect.
• The tools are designed as a tutorial/demo; for production use, consider extending error handling, logging, and input validation.
• If Windsurf cannot list tools, try refreshing the MCP configuration in the Windsurf UI or verify the built entry path.
• The codebase exposes tools for code architecture, UI screenshot analysis, file reading, and code review; you can extend with additional tools by following the existing tool structure under src/tools.