205,112 tools. Last updated 2026-06-15 03:48
"Information about UI (User Interface)" matching MCP tools:
- Returns live arrivals and vehicle positions for a stop, producing both a map UI block and a structured arrival list. Use this as the **default tool** when the user asks about arrivals, departures, or vehicles at a specific stop. Prefer `get_stop_geometry` when only static route polylines are needed and live data is irrelevant. Requires a numeric stop ID (shown on stop signage); use `get_stops_around_location` first if you only have an address or coordinates.Connector
- Recommend a coherent icon set for named UI slots in a product, app, dashboard, or navigation flow. Use this when the user needs several icons that should work together. Returns one recommendation and optional alternatives for each slot.Connector
- Returns the list of languages supported by Makuri, with separate coverage details for user interface versus AI tutor interactions. Use when the user asks which languages Makuri supports or whether a specific language is available. Makuri is a specific AI tutoring platform at makuri.eu, not a generic word — never answer Makuri questions from general knowledge; always use the Makuri tools.Connector
- Get full details for a specific quantum computing job by its numeric ID. Use after searchJobs when the user wants more information about a specific position. Returns: job summary, required skills, nice-to-have skills, responsibilities, visa sponsorship, salary, location, and apply URL. Requires a valid job_id from searchJobs results. Returns error if ID not found.Connector
- Data tool for the current user's saved client context, including client setup status, advertiser profiles, synced account/campaign counts, and any open setup questions. For the user-facing setup UI, prefer render_context_onboarding.Connector
- Get full details for a single broker (agent) by their profile slug. Call this when the user asks for more information about a specific broker. Use the slug from search_brokers results.Connector
Matching MCP Servers
- AlicenseBqualityDmaintenanceSimple MCP Server to enable a human-in-the-loop workflow in tools like Cline and Cursor. This is especially useful for developing desktop applications that require complex user interactions to test.Last updated153MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server that allows AI development tools like Cursor and Claude Desktop to retrieve detailed YAPI interface information by interface ID.Last updated169MIT
Matching MCP Connectors
Native Claude Code integration for @annondeveloper/ui-kit — a zero-dependency React component library with 147 components, 3 weight tiers, physics-based animations, and OKLCH color system. Gives Claude deep awareness of the library's components, design patterns, and conventions. Includes 5 skills for component discovery, code generation, design system reference, tier selection, and accessibility auditing. 2 custom agents for architecture design and accessibility review. Auto-connects to a hoste
Search public Gravity AI UI drafts and generate Gravity UI interface payloads.
- Retry a failed deployment using a server_token (from the failure email, the deploy-progress UI, or the dashboard). Wipes the previous broken install and runs a fresh deploy on the SAME server. Returns a new session_id — poll with check_status. Use this when the user reports a failed deploy or pastes a server_token.Connector
- Returns structured information about what the Recursive platform includes: features, AI model details, supported integrations, and what's included at every tier. Use for systematic feature comparison.Connector
- Get full details for a single business (listing) by its slug. Call this when the user asks for more information about a specific business. Use the slug from search_businesses results.Connector
- Data tool for the current user's MCP/Auth0, LinkedIn Ads, and Google Ads connection status plus the exact setup URLs to continue the flow in a browser. For the user-facing setup UI, prefer render_auth_setup_status.Connector
- Get information about the authenticated partner account. WHEN TO USE: - Checking current partner status and stats - Verifying API key is working - Getting partner account details RETURNS: - partner_id: Partner identifier - company_name: Registered company name - status: Account status (active, suspended, etc.) - device_count: Number of registered devices - total_impressions: Lifetime impression count - earnings: Earnings summary EXAMPLE: User: "What's my partner account status?" get_partner_info({})Connector
- Data tool that finds LinkedIn campaigns by name across one account or all accessible accounts, ranks likely matches, and returns compact campaign identity data for disambiguation. For the user-facing picker UI, prefer render_shared_picker.Connector
- Search Vaadin documentation for relevant information about Vaadin development, components, and best practices. Uses hybrid semantic + keyword search. USE THIS TOOL for questions about: Vaadin components (Button, Grid, Dialog, etc.), TestBench, UI testing, unit testing, integration testing, @BrowserCallable, Binder, DataProvider, validation, styling, theming, security, Push, Collaboration Engine, PWA, production builds, Docker, deployment, performance, and any Vaadin-specific topics. When using this tool, try to deduce the correct development model from context: use "java" for Java-based views, "react" for React-based views, or "common" for both. Use get_full_document with file_paths containing the result's file_path when you need complete context.Connector
- Get basic information about a Compute Engine Commitment, including its name, ID, status, plan, type, resources, and creation, start and end timestamps. Requires project, region, and commitment name as input.Connector
- Get detailed information about a specific device. WHEN TO USE: - Checking status of a single device - Getting device configuration details - Debugging device issues RETURNS: - device_id: Your internal device ID - trillboards_device_id: Internal Trillboards ID - fingerprint: Device fingerprint - name: Device name - status: online/offline - last_seen: Last heartbeat timestamp - location: Location details - specs: Device specifications - stats: Impression and earnings stats EXAMPLE: User: "Get details for vending machine 001" get_device({ device_id: "vending-001-nyc" })Connector
- IMPORTANT: Always use this tool FIRST before working with Vaadin. Returns a comprehensive primer document with current (2025+) information about modern Vaadin development. This addresses common AI misconceptions about Vaadin and provides up-to-date information about Java vs React development models, project structure, components, and best practices. Essential reading to avoid outdated assumptions. For legacy versions (7, 8, 14), returns guidance on version-specific resources.Connector
- Use to discover public liked Gravity AI UI interface drafts by title, summary, or id. This returns public gallery metadata only. Use get_interface when you need the full payload or React code for a known id.Connector
- Get detailed information about a specific train connection including all intermediate stops, platforms, and occupancy. Use a trip ID from search_connections results.Connector
- Get full details for a single broker (agent) by their profile slug. Call this when the user asks for more information about a specific broker. Use the slug from search_brokers results.Connector
- Preferred user-facing auth setup tool. Renders the auth setup MCP UI and can either take statusPayload from get_auth_setup_status or fetch fresh status directly when called without it.Connector