"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 Codex and Claude Code agents to submit drafts for local rubric-based review through TypeSafe Jev, returning keep, rewrite, or uncertain decisions so agents can fix flagged issues and re-check once.

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.

Enables MCP clients to turn Make blueprints and Zapier exports into n8n workflow files, with a per-step report of what converted, what to review, and what must be finished by hand. Also lists zaps, explains how individual steps are handled, checks workflow files for broken links or placeholders, and can upload the result to an n8n instance as an inactive workflow.

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

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.

Enables users to turn any API's documentation into a tested MCP server whose tools expose the API's own operations, with linting, contract tests, and live verification. It accepts OpenAPI/Swagger, Postman, RAML, WSDL, GraphQL, RSS, and HTML docs.

Enables turning requirements documents into RFCs, functional test scenarios, and a traceability matrix, with tools to parse, diff, and verify coverage.

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

Enables read-only collection and comparison of Google Search Console and Bing Webmaster data, conservative URL protection, content auditing, reviewed-build verification, and private report generation through ten typed tools over stdio.

Enables an MCP-compatible AI client to author Blender Python, run Blender, import the resulting asset into Unity with materials and a prefab, place it in the active scene, verify the import, and revise the same asset using stable IDs.

Enables AI assistants to query PostgreSQL, MySQL, SQL Server, Oracle, and MongoDB databases through MCP with read-only, audited access.

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.

Deterministic Markdown-to-Word (.docx) publishing compiler with native OMML equations, three-line tables, CSL citations, and quality gates for AI agents.

Converts any Python Click or Typer CLI into an MCP server automatically — zero-code transformation that introspects CLI commands and exposes them as MCP tools.

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).

Enables an MCP client to retrieve explicitly allowlisted Markdown context, create and read local task contracts, write local handoffs, and return locally configured routing metadata without invoking a model, executing commands, or writing to the vault.

Enables AI assistants to call any SOAP/WSDL web service as MCP tools, automatically converting each WSDL operation into a callable tool with authentication and security controls.

Enables users to record, review, verify, and expose permitted browser workflows as callable MCP tools with typed inputs, isolated Chromium verification, and approval-gated writes.

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.

Turns any OpenAPI/Swagger or REST API into callable MCP tools for Claude, ChatGPT, Copilot, and Cursor, with secure authentication and role-based access control.

Enables agentic co-authoring of feature specs, decomposition into architecture-validated tickets, and idempotent syncing to Linear as projects with epics, sub-issues, and dependencies.

Turns any OpenAPI/Swagger specification into a functional MCP server, dynamically exposing API endpoints as LLM tools or generating standalone Python code.

Enables agents to turn a plain-language description of a device into a complete, validated build package — parts list, 3D-printable parts, wiring, firmware code, picture assembly guide, and tests — that anyone can assemble without electronics experience.

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