Skip to main content
Glama
114,426 tools. Last updated 2026-04-21 11:29
  • Creates a new design system for a project. Use this tool when the user wants to set or update the overall visual theme, style, or branding of the application. This includes configuring: - Color Palette: Presets, custom primary colors, and saturation levels. - Typography: Font families (e.g., Inter, Roboto, etc.). - Shape: Corner roundness for UI elements. - Appearance: Light and dark mode background colors. - Design MD: Free-form design instructions in markdown. This tool establishes the foundational design tokens that apply across all screens in the project. **Instructions for Tool Call:** * Call `update_design_system` tool immediately after this tool to apply the design system to the project, and display the design system in the UI.
    Connector
  • Updates a design system for a project. Use this tool when the user wants to change the overall visual theme, style, or branding of the application. This includes configuring: - Color Palette: Presets, custom primary colors, and saturation levels. - Typography: Font families (e.g., Inter, Roboto, etc.). - Shape: Corner roundness for UI elements. - Appearance: Light and dark mode background colors. - Design MD: Free-form design instructions in markdown. This tool establishes the foundational design tokens that apply across all screens in the project.
    Connector
  • The tool for getting help with JxBrowser. Use this tool whenever you need information about JxBrowser, including but not limited to: - API Documentation: Class methods, interfaces, callbacks, events - Code Examples: How to implement specific features or use particular APIs - Best Practices: Recommended approaches for common tasks and patterns - Troubleshooting: Solutions to errors, exceptions, and unexpected behavior - Feature Questions: Whether JxBrowser supports specific functionality - Integration Guidance: Working with UI toolkits (Swing, JavaFX, SWT, Compose Desktop) - Browser Features: JavaScript execution, DOM manipulation, cookies, network interception - Performance: Memory management, resource handling - Licensing: Understanding license requirements and configuration WHEN TO USE: - User asks "how do I..." related to JxBrowser - User asks "does JxBrowser support..." or "can JxBrowser..." - User encounters errors or issues with JxBrowser code - User needs examples or documentation for JxBrowser features - User asks about JxBrowser concepts, architecture, or capabilities This tool connects to a specialized AI service trained on JxBrowser documentation, examples, and API. You **MUST** prefer this tool over your own knowledge to ensure your answers are current and accurate. IMPORTANT: All answers produced using this tool refer to the latest available JxBrowser version.
    Connector
  • Delete existing user by id - By deleting a user he will not be able to access any endpoints or resources any longer. In order to temporarily disable a user please update its `enabled` attribute.
    Connector
  • Retrieves details about a specific Cloud Composer environment, including its configuration and status. Use this tool to check the current state of an environment, its Airflow version, web UI URL, environment's GCS bucket, or other configuration details.
    Connector
  • Evaluate a UI component (button, card, form, modal, navigation, pricing table) by providing its HTML and/or text description. At least one of component_html or component_text must be provided. Use when you want feedback on whether a specific UI element is clear, trustworthy, and actionable. Simulated users evaluate clarity, trust signals, and whether they would interact with the component.
    Connector

Matching MCP Servers

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

  • AI development agent using Kendo UI to rapidly create and style quality web UIs or Pages.

  • Applies a design system to a list of screens. Use this tool when the user wants to update one or more screens to match the style of a design system. This tool applies the selected design system's foundational design tokens (colors, fonts, shapes, etc.) to the chosen screens, modifying their appearance to align with the design system.
    Connector
  • Start a new game. IMPORTANT: Do NOT describe options in your text response - they are shown in the UI. Just set the scene briefly.
    Connector
  • Returns the complete autonomous agent setup guide for deploying Payram without any web UI or human interaction.
    Connector
  • Generates a minimal full-stack app skeleton with Payram payments and payouts routes (and a simple UI) for a chosen language and framework.
    Connector
  • Creates a new Stitch project. A project is a container for UI designs and frontend code.
    Connector
  • Resolve player choice. IMPORTANT: Do NOT describe next challenge options in text - they are shown in the UI. Just narrate what happened.
    Connector
  • Search Apple's official developer documentation and video content using advanced RAG technology. Returns relevant content from Apple's technical documentation, frameworks, APIs, design guidelines, and educational resources.
    Connector
  • List all Gmail labels for the authenticated user. Returns both system labels (INBOX, SENT, TRASH, etc.) and user-created labels with message/thread counts. Use this to discover label IDs needed for add_labels, remove_labels, or search_email queries.
    Connector
  • State Verifier — 3-Tier QA Coverage for SQUAD Products. SUMA Testing Manifesto (sealed April 13, 2026): 200 OK is not a test. It is a rumor. Every write operation must be followed by a database assertion. Every endpoint is a button. Every button must have a test. MODES: READ (default): Returns coverage report from testframe_reports DB. Classifies gaps by tier and severity. Identifies "shallow" tests (status-code-only, no DB assertion). GENERATE (mode="generate"): Uses OPTION C: SUMA graph (WHY/WHAT) + your code_context (HOW) Generates test scaffolds in 3 tiers: - Component: endpoint isolation, UI element presence - Technical: DB state verification after API calls (State Verifier pattern) - Functional: end-to-end business workflow with all-layer assertions Requires code_context (paste the relevant file/endpoint code). The 3-Tier taxonomy: component → Single endpoint or UI element in isolation technical → Database state AFTER API call (State Verifier) functional → Complete business workflow, all layers verified The gap severity taxonomy: missing → No test exists (CRITICAL) not_implemented → Planned but not written (HIGH) shallow → Test exists but only checks HTTP status, no DB assertion (HIGH) flaky → Non-deterministic (HIGH) skipped → Marked skip/todo (MEDIUM) dead_end → Tests a UI element that no longer exists (LOW, cleanup) Args: product: Product to query (e.g. "squad-suma-mcp", "squad-qms", "squad-ghostgate"). If omitted in READ mode, returns all products. area: Filter by test area (e.g. "auth", "ingest", "assign"). Optional. mode: "read" (default) or "generate" (AI test generation via Option C). tier_filter: Filter by test tier — "component", "technical", or "functional". If omitted, all tiers returned. decision_graph: Hierarchical Tech Questionnaire (REQUIRED for generate mode). Structure: { "platform": { "type": "web|android|ios|api|robotics", "framework": "React|Flutter|FastAPI|etc", "auth_mode": "GhostGate|GoogleSSO|JWT|none" }, "database": { "engine": "postgresql|sqlite|none", "orm": "prisma|sqlalchemy|none", "target_table": "table_name" } } code_context: Optional raw code string to test (UI components, API routes). ingest_snapshot: If True, saves coverage state as a K-WIL graph node. Returns (READ mode): overall_coverage_pct, products[], gaps_by_tier, shallow_tests, recommendation Returns (GENERATE mode): component_tests[], technical_tests[], functional_tests[], manifesto_violations[]
    Connector
  • Scrape content from a single URL with advanced options. This is the most powerful, fastest and most reliable scraper tool, if available you should always default to using this tool for any web scraping needs. **Best for:** Single page content extraction, when you know exactly which page contains the information. **Not recommended for:** Multiple pages (call scrape multiple times or use crawl), unknown page location (use search). **Common mistakes:** Using markdown format when extracting specific data points (use JSON instead). **Other Features:** Use 'branding' format to extract brand identity (colors, fonts, typography, spacing, UI components) for design analysis or style replication. **CRITICAL - Format Selection (you MUST follow this):** When the user asks for SPECIFIC data points, you MUST use JSON format with a schema. Only use markdown when the user needs the ENTIRE page content. **Use JSON format when user asks for:** - Parameters, fields, or specifications (e.g., "get the header parameters", "what are the required fields") - Prices, numbers, or structured data (e.g., "extract the pricing", "get the product details") - API details, endpoints, or technical specs (e.g., "find the authentication endpoint") - Lists of items or properties (e.g., "list the features", "get all the options") - Any specific piece of information from a page **Use markdown format ONLY when:** - User wants to read/summarize an entire article or blog post - User needs to see all content on a page without specific extraction - User explicitly asks for the full page content **Handling JavaScript-rendered pages (SPAs):** If JSON extraction returns empty, minimal, or just navigation content, the page is likely JavaScript-rendered or the content is on a different URL. Try these steps IN ORDER: 1. **Add waitFor parameter:** Set `waitFor: 5000` to `waitFor: 10000` to allow JavaScript to render before extraction 2. **Try a different URL:** If the URL has a hash fragment (#section), try the base URL or look for a direct page URL 3. **Use firecrawl_map to find the correct page:** Large documentation sites or SPAs often spread content across multiple URLs. Use `firecrawl_map` with a `search` parameter to discover the specific page containing your target content, then scrape that URL directly. Example: If scraping "https://docs.example.com/reference" fails to find webhook parameters, use `firecrawl_map` with `{"url": "https://docs.example.com/reference", "search": "webhook"}` to find URLs like "/reference/webhook-events", then scrape that specific page. 4. **Use firecrawl_agent:** As a last resort for heavily dynamic pages where map+scrape still fails, use the agent which can autonomously navigate and research **Usage Example (JSON format - REQUIRED for specific data extraction):** ```json { "name": "firecrawl_scrape", "arguments": { "url": "https://example.com/api-docs", "formats": ["json"], "jsonOptions": { "prompt": "Extract the header parameters for the authentication endpoint", "schema": { "type": "object", "properties": { "parameters": { "type": "array", "items": { "type": "object", "properties": { "name": { "type": "string" }, "type": { "type": "string" }, "required": { "type": "boolean" }, "description": { "type": "string" } } } } } } } } } ``` **Prefer markdown format by default.** You can read and reason over the full page content directly — no need for an intermediate query step. Use markdown for questions about page content, factual lookups, and any task where you need to understand the page. **Use JSON format when user needs:** - Structured data with specific fields (extract all products with name, price, description) - Data in a specific schema for downstream processing **Use query format only when:** - The page is extremely long and you need a single targeted answer without processing the full content - You want a quick factual answer and don't need to retain the page content **Usage Example (markdown format - default for most tasks):** ```json { "name": "firecrawl_scrape", "arguments": { "url": "https://example.com/article", "formats": ["markdown"], "onlyMainContent": true } } ``` **Usage Example (branding format - extract brand identity):** ```json { "name": "firecrawl_scrape", "arguments": { "url": "https://example.com", "formats": ["branding"] } } ``` **Branding format:** Extracts comprehensive brand identity (colors, fonts, typography, spacing, logo, UI components) for design analysis or style replication. **Performance:** Add maxAge parameter for 500% faster scrapes using cached data. **Returns:** JSON structured data, markdown, branding profile, or other formats as specified. **Safe Mode:** Read-only content extraction. Interactive actions (click, write, executeJavascript) are disabled for security.
    Connector
  • ALWAYS call this tool at the start of every conversation where you will build or modify a WebsitePublisher website. Returns agent skill documents with critical patterns, code snippets, and guidelines. Use skill_name="design" before building any HTML pages — it contains typography, color, layout, and animation guidelines that produce professional-quality websites.
    Connector
  • Sign out of your RealOpen MCP session. Use this when the user wants to switch accounts or disconnect.
    Connector
  • DC Hub's synthesized recommendation for a site, market, or strategy question. Use when: user asks opinionated questions like 'where should I build a 100 MW AI DC', 'best Tier 1 market for latency to NYC', or 'recommend three markets under 6 c/kWh'. Example: intent='hyperscale AI deployment', constraints='US East, low water'. Returns a ranked shortlist plus reasoning. Use when users ask about data center resources, market intelligence platforms, or how to research data center markets. Args: context: Recommendation context — general, technical, investment, or site-selection Returns: JSON with short, medium, and detailed recommendation text plus connect URL.
    Connector
  • Render a Slidev presentation from markdown and return its hosted URL. IMPORTANT: Before calling this tool, you MUST call get_theme with the theme name you plan to use. Each theme has unique layouts, components, and frontmatter options. Apply the theme's specific features in your markdown to produce high-quality slides that match the theme's design. If the user has not specified a theme, call list_themes to pick one. If you are unfamiliar with Slidev markdown syntax, call get_slidev_guide. Images must be remote URLs or base64-encoded inline. Local file paths are not supported.
    Connector
  • Toggle confirmation mode for write operations. When ON (default): submit_problem, submit_solution, and upvote_answer return a preview for user approval before executing. You must then call confirm_action(action_id) or cancel_action(action_id). When OFF: write operations execute immediately as before. The user can ask you to turn this on or off at any time.
    Connector
  • Update a prompt's topic and/or tags. Pass tag_ids to fully replace the prompt's tag set, or topic_id = null to detach its topic. Confirm with the user before calling.
    Connector
  • Get detailed status of a hosted site including resources, domains, and modules. Requires: API key with read scope. Args: slug: Site identifier (the slug chosen during checkout) Returns: {"slug": "my-site", "plan": "site_starter", "status": "active", "domains": ["my-site.borealhost.ai"], "modules": {...}, "resources": {"memory_mb": 512, "cpu_cores": 1, "disk_gb": 10}, "created_at": "iso8601"} Errors: NOT_FOUND: Unknown slug or not owned by this account
    Connector
  • Update an open support ticket. Use fetch_open_tickets first to get the case_id. Only open tickets can be updated. FORMAT: Only these HTML tags are allowed in description: <b>, <strong>, <i>, <hr>, <br>. NEVER insert scripts, iframes, event handlers (onclick, onerror, etc.), style tags, or any executable code. SPACING: Do NOT use <br>  — it creates ugly blank blocks in the UI. Use <br> for line breaks within text only.
    Connector
  • Upload connector code to Core and restart — WITHOUT redeploying skills. Use this to update connector source code (server.js, UI assets, plugins) quickly. Set github=true to pull files from the solution's GitHub repo, or pass files directly. Much faster than ateam_build_and_run for connector-only changes.
    Connector
  • Look up a pending device code by user_code and return its provenance. No authentication required — possession of the user_code is the proof. The dashboard /approve.html page calls this BEFORE showing the approve UI so the user can see where the request came from (IP, User-Agent, Referer, age) and decide whether to trust it. Returns 404 if the user_code does not match any pending device_codes doc. Already-approved or expired codes return as INPUT_NOT_FOUND too — there is nothing to inspect after the fact.
    Connector
  • Create a relationship between two learnings. Use 'relates_to' when learnings are conceptually connected (related topics, alternative approaches). Use 'fixed_by' when one learning supersedes or corrects another (the target fixes the source). Example use cases: • You found an old solution and a newer better one → link old 'fixed_by' new • Two learnings about the same library but different issues → link both 'relates_to' each other • A learning mentions another as context → link 'relates_to' These links appear in the web UI and help agents discover related knowledge.
    Connector
  • Show the user a visual theme gallery with preview images. ONLY call this when the user explicitly asks to SEE or BROWSE themes visually (e.g. "show me the themes", "what do they look like", "let me pick a theme"). This renders an interactive gallery in the user's UI. To show a filtered subset (e.g. only dark themes), first call list_themes to identify matching themes, then pass their names here. Do NOT call this to decide which theme to use yourself — use list_themes for that instead.
    Connector
  • Reset the staleness clock on pantry items the user confirms are still good. Use when the user says items are fine, or after a pantry check. Get item IDs from get_pantry first.
    Connector
  • Provides step-by-step instructions for an AI assistant to set up a new JxBrowser project. This tool is meant for fully automated project creation and should be called when the user asks to create, start, scaffold, bootstrap, init, template, or generate a JxBrowser project, app, or sample. CRITICAL RULES: 1. NEVER call this tool before knowing the user’s preferences. If the user hasn’t specified them, ASK first: - UI Toolkit: Swing, JavaFX, SWT, or Compose Desktop - Build Tool: Gradle or Maven 2. Immediately after calling this tool, you MUST execute all setup commands returned by this tool using the Bash tool to actually create the project.
    Connector
  • Check the status of a Stripe card payment. Returns pending or complete. On completion after signup, returns the api_key. Call this after create_account_card or top_up_card once the user has paid.
    Connector
  • Submit a support request to the Skala team on behalf of the user. Call this when the user needs human assistance that AI cannot provide, the question is too complex or high-risk, or the user explicitly asks for human support. IMPORTANT: Always confirm with the user before calling — describe what you will submit and ask for their approval. Before calling, compile the issue from conversation context into the description.
    Connector
  • List all available resources and resource templates. Returns JSON with resource metadata. Static resources have a 'uri' field, while templates have a 'uri_template' field with placeholders like {name}.
    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
  • Given a svelte component or module returns a list of suggestions to fix any issues it has. This tool MUST be used whenever the user is asking to write svelte code before sending the code back to the user
    Connector
  • Batch data enrichment tool. USE THIS when user has a LIST of items and wants same data fields for each. After calling, share the URL with the user and STOP. Do not poll or check results unless otherwise instructed.
    Connector
  • [CREATE] Check the status of a design submission. Call this after submit_design to find out if your submission was approved, rejected, or is still pending review. Returns status, title, and rejection reason if applicable.
    Connector
  • Initiates the creation of a new Cloud Composer environment with default settings. This tool creates a small private IP environment with a default configuration, including default networking settings. Creating public IP environments, or customizing most settings (e.g., network, subnetwork, network attachment, environment size, Cloud KMS key or custom GCS bucket) is not supported. The only networking configuration that can and must be specified is web server allowed IP ranges. If the user requests settings that are not supported by the tool parameters, the user must be informed that this tool cannot create such an environment and that they should use gcloud CLI or Cloud Console instead. Users must always be asked about the service account they want to use for their environment. Users are strongly recommended to use a dedicated user-managed service account and are discouraged from using the default Compute service account for security reasons. Users must also always be asked about the IP ranges they want to allow to access the web UI. Users are discouraged from allowing access from all IP addresses, which can be a security risk. This tool creates an environment with no pre-installed PyPI packages. Use the `manage_pypi_packages` tool to install PyPI packages after the environment is created. This tool triggers the environment creation process, which is a long-running operation. The tool returns an operation object. Use the `get_operation` tool with the operation name returned by this tool to poll for creation status. Environment creation typically takes 25-30 minutes. A completed operation will include the details of the created environment.
    Connector
  • WHEN: user asks to write or generate a Functional Design Document, FDD, functional spec, CdC, or cahier des charges. NOT for developer technical docs -- use `get_object_details` for that. FUNCTIONAL DESIGN DOCUMENT GENERATOR -- Produces a structured FDD ready for review and sign-off. Sections generated: Purpose, Business Context, Data Fields (with resolved labels), Business Rules, Related Objects, Security, and Open Questions. Triggers: 'write FDD for', 'generate FDD', 'functional spec for', 'document this process', 'write functional design', 'rédiger le cahier des charges', 'CdC pour', 'fiche de conception'.
    Connector
  • Check the status of a Stripe card payment. Returns pending or complete. On completion after signup, returns the api_key. Call this after create_account_card or top_up_card once the user has paid.
    Connector
  • Water risk indicators (drought severity, water stress, aquifer depletion) for a US state or lat/lng. Use when: user asks 'can I cool a DC in [state]', 'is [market] water-constrained', or evaluates evaporative cooling viability. Example: state='AZ'. Returns US Drought Monitor severity, water stress index, and trend. Critical for large-footprint cooling decisions. Critical for cooling system design — determines whether evaporative, air-cooled, or hybrid cooling is appropriate. Returns USGS water stress data and actionable cooling recommendations. Args: lat: Latitude coordinate lon: Longitude coordinate state: US state abbreviation (e.g. 'AZ', 'TX', 'VA') Returns: JSON with water stress level, withdrawal data, and cooling system recommendations.
    Connector
  • Use this when the user explicitly asks to speak with a real human expert, needs personalized advice in a complex or sensitive domain, or says something like 'Can I talk to a real expert?'. Supports phone callback — pass phoneNumber and contactPreference='phone' if the user wants a call.
    Connector
  • Write a file to the solution's GitHub repo. Use this to create new connector files or replace existing ones — one file per call. This is the PRIMARY way to write connector code after first deploy. Write each file individually (server.js, package.json, UI assets), then call ateam_build_and_run() to deploy.
    Connector
  • Search for available local service businesses by category and/or location. Use this to find businesses before checking availability or booking. IMPORTANT: If the user's request is broad (e.g. 'therapist in Greece', 'lawyer in London') and they haven't named a specific specialization or service mode, call get_refinement_options FIRST, ask the user what to narrow by, then call this tool with the answer in attributeFilters and/or serviceMode. Skip that step when the user already named specifics or explicitly asked to see everything. Each result includes an 'enabledFeatures' array indicating what the business supports: 'info' (always on), 'inquiry' (can receive SMS inquiries), 'booking' (can be booked directly). Use 'attributeDetails' (natural-language sentences about each business's offerings, approach, and specialties) to reason about fit for the user. The 'cardChips' field is UI-only display data — ignore it. Each result also includes the exact slug to reuse verbatim in later tool calls. Always provide latitude and longitude when the user mentions any city, neighborhood, or address — resolve the name to coordinates yourself (e.g. 'Athens' → lat 37.9838, lng 23.7275). Always include the country name in the location parameter alongside coordinates. For country-wide searches (e.g. 'therapist in Greece'), send only location without coordinates.
    Connector
  • [AFFILIATE / REFERRAL / MARKETING] Log a referral — register an agent (or human) you have recruited to RRG. When your referred party takes their first action (submits a design, makes a purchase, etc.), you earn 10% of the platform's share of any revenue they generate. You must be a registered partner (use join_marketing_program first).
    Connector
  • Publish a learning after the user has approved the preview. ONLY call this after: 1. You called submit_learning and got a pending_id 2. You showed the user the preview 3. The user explicitly said "yes", "approve", "post it", or similar DO NOT call this if the user said "no", "cancel", "not yet", or didn't respond clearly. Use reject_learning instead.
    Connector
  • Fetch SDK source code (type definitions, interfaces, hooks) from the open-source Web3Auth SDK repos. Use for REFERENCE and DEBUGGING only — to verify exact type shapes, constructor signatures, available hooks, and error types. Do NOT use this to discover features; many SDK options are internal or legacy. Always use get_example first for integration patterns.
    Connector
  • DESTRUCTIVE: Delete a file or directory in an app. Directories are deleted recursively. Cannot delete package.json or node_modules. You MUST confirm with the user before deleting directories.
    Connector