"Quest" matching MCP servers:

Enables Claude Code to see and control a Meta Quest headset via ADB, providing tools for screenshots, logs, performance monitoring, app management, and more.

Provides an interactive user interface for asking questions with support for text inputs, single/multi-select options, and confirmation dialogs. It allows LLMs to gather structured input or feedback from users through a set of predefined input types.

Enables Claude to design and build interactive 3D games within the Portals virtual platform through direct API integration. It facilitates automated asset placement, interaction logic configuration, and quest management using natural language commands.

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.

Enables Windows-based AI assistants to run Oculus/Meta Quest Link diagnostics, capture VR screenshots and telemetry, inspect headset/controller state, and apply reversible performance-tuning and Link settings.

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 structured input surfaces inside Claude conversations with prefilled forms, assumption ledgers, and review matrices, so the agent can infer values and present proposals for auditing rather than authoring from scratch.

Just to be clear about the final JSON: the MCP server is named herdr-inbox, and it enables Claude Code agents in herdr to ask questions asynchronously without stalling, with all open questions answered from one popup and answers routed back to the asking agent.

Enables AI agents to query component governance rules, validate component props, and generate development prompts for questionnaire editors.