AI SummaryMCP Server that integrates Bing Search API into Windsurf, enabling developers to perform web searches directly within their development environment while following strict project guidelines on package management and code quality.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to add the "bing-search-mcp — Windsurf Rules" prompt rules to my project. Repository: https://github.com/leehanchung/bing-search-mcp Please read the repo to find the rules/prompt file, then: 1. Download it to the correct location (.cursorrules, .windsurfrules, .github/prompts/, or project root — based on the file type) 2. If there's an existing rules file, merge the new rules in rather than overwriting 3. Confirm what was added
Description
MCP Server for Bing Search API
Server Capabilities
| Capability | Feature Flag | Description | |-------------|------------------------------|------------------------------------| | prompts | listChanged | Prompt template management | | resources | subscribe<br/>listChanged| Resource exposure and updates | | tools | listChanged | Tool discovery and execution | | logging | - | Server logging configuration | | completion| - | Argument completion suggestions |
Development Guidelines
This document contains critical information about working with this codebase. Follow these guidelines precisely.
Core Development Rules
• Package Management • ONLY use uv, NEVER pip • Installation: uv add package • Running tools: uv run tool • Upgrading: uv add --dev package --upgrade-package package • FORBIDDEN: uv pip install, @latest syntax • Code Quality • Type hints required for all code • Public APIs must have docstrings • Functions must be focused and small • Follow existing patterns exactly • Line length: 88 chars maximum • Testing Requirements • Framework: uv run pytest • Async testing: use anyio, not asyncio • Coverage: test edge cases and errors • New features require tests • Bug fixes require regression tests • For commits fixing bugs or adding features based on user reports add: `bash git commit --trailer "Reported-by:<name>" ` Where <name> is the name of the user. • For commits related to a Github issue, add `bash git commit --trailer "Github-Issue:#<number>" ` • NEVER ever mention a co-authored-by or similar aspects. In particular, never mention the tool used to create the commit message or PR.
Pull Requests
• Create a detailed message of what changed. Focus on the high level description of the problem it tries to solve, and how it is solved. Don't go into the specifics of the code unless it adds clarity. • Always add leehanchung as reviewer. • NEVER ever mention a co-authored-by or similar aspects. In particular, never mention the tool used to create the commit message or PR.
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster
Works With
Any AI assistant that accepts custom rules or system prompts