"Using Bing Search to Answer Questions" matching MCP servers:

Enables AI models to ask users questions through a local web interface, supporting batch questions, multi-select, and free text for human-in-the-loop interactions.

Enables to interact with the Bing Webmaster Tools API for managing sites, URLs, sitemaps, and viewing analytics.

Converts AI Skills (following Claude Skills format) into MCP server resources, enabling LLM applications to discover, access, and utilize self-contained skill directories through the Model Context Protocol. Provides tools to list available skills, retrieve skill details and content, and read supporting files with security protections.

MCP server for AI agents to send notifications, copy to clipboard, request confirmations, and collect text input from users across their devices.

A Model Context Protocol (MCP) server that gives your AI assistant the power to convert Markdown into 14 professional document formats — PDF, DOCX, HTML, LaTeX, CSV, JSON, XML, XLSX, RTF, PNG, and more. Stop copy-pasting. Let the AI do the exporting.

Routes one brief to the right image model across 60+ (gpt-image-1.5, Ideogram 3, Recraft V4, Flux), validates the output, and fans out to iOS/Android/PWA/favicon/visionOS/Flutter bundles. Works without an API key via Pollinations, HF Inference, Stable Horde, or host-LLM inline SVG.

A Model Context Protocol server that converts Markdown content to HTML format.

Generates standalone, human-readable MCP servers from RAML 1.0 or OpenAPI 3.x specs, exposing one tool per resource and method that makes real HTTP calls. It understands Mule/Anypoint auth patterns such as Client ID enforcement and OAuth2, wiring the expected credentials from environment variables at call time.

Turns any OpenAPI REST or GraphQL API into an MCP server, allowing AI assistants like Claude to interact with APIs without writing code.

Enables existing Express routers to be exposed as MCP tools, dispatching tool calls through the Express middleware stack in-process without a network hop.

Auto-generates MCP tools from your OpenAPI spec, allowing natural language interaction with any API via configurable headers and serverless deployment.

A bridge that enables any LLM to access and interact with documented REST APIs through the Model Context Protocol (MCP).

A minimal MCP server that auto-generates tools from your OpenAPI spec, optimized for Vercel.

A standalone proxy that transforms any OpenAPI or Swagger-described REST API into an MCP server by mapping API operations to executable MCP tools. It enables AI clients to interact with existing web services through automated HTTP requests based on their official documentation.

Transform Figma designs into pixel-perfect React + Tailwind components using the Model Context Protocol.

Generates AI-powered clarifying questions for user task requests using Claude, helping gather detailed requirements about tech stack, architecture, deployment, and project scope through categorized, contextually relevant questions.

Automatically converts Swagger/OpenAPI specifications into dynamic MCP tools, enabling interaction with any REST API through natural language by loading specs from local files or URLs.

Provides local web search (Baidu, Bing, 360, Sogou), page scraping to markdown, and image description via LM Studio vision models, all without external APIs and with disk caching.

Converts any REST API endpoints into MCP tools, enabling AI clients like Cursor and Claude Desktop to call internal services directly.

An MCP server that allows coding agents to search the Swift Package Index and retrieve GitHub READMEs without requiring an API key. It features comprehensive search filters for stars, platforms, and licenses, providing token-efficient responses optimized for LLM comprehension.