Skip to main content
Glama
134,434 tools. Last updated 2026-05-23 18:02

"A server for finding vibe code or vibe-related programming content" matching MCP tools:

  • Sets or clears the default idle content for a display. Idle content is shown whenever the display has no active live content. Provide html OR url to set idle content (mutually exclusive — url is wrapped in a full-page iframe document), or omit both to clear idle content. Provide content_description to make later state reads easier for agents. When the display is currently idle (no active live content), the new idle is pushed to the display immediately; otherwise it stays dormant until the live content ends. Requires admin scope.
    Connector
  • Semantic search across the user's entire library by meaning, theme, or vibe. Searches every book/movie/album/show/anime as one corpus. Use for cross-media or thematic questions like "things about grief" or "noir mood". For specific title/creator lookups, use the keyword `search` tool instead.
    Connector
  • Lookup FDA device classification details by product code. Returns device name, device class (I/II/III), medical specialty, regulation number, review panel, submission type, and definition. Requires: product code (3-letter code from 510(k), PMA, or device product listings). Related: fda_product_code_lookup (cross-reference across 510(k) and PMA), fda_search_510k (clearances for this product code), fda_search_pma (PMA approvals for this product code).
    Connector
  • Answer questions using knowledge base (uploaded documents, handbooks, files). Use for QUESTIONS that need an answer synthesized from documents or messages. Returns an evidence pack with source citations, KG entities, and extracted numbers. Modes: - 'auto' (default): Smart routing — works for most questions - 'rag': Semantic search across documents & messages - 'entity': Entity-centric queries (e.g., 'Tell me about [entity]') - 'relationship': Two-entity queries (e.g., 'How is [entity A] related to [entity B]?') Examples: - 'What did we discuss about the budget?' → knowledge.query - 'Tell me about [entity]' → knowledge.query mode=entity - 'How is [A] related to [B]?' → knowledge.query mode=relationship NOT for finding/listing files, threads, or links — use workspace.search for that.
    Connector
  • List vibes available to the authenticated user. Returns vibe IDs, names, and sources (system or custom) that can be passed as vibe_id to generate_presentation.
    Connector
  • Reads the raw HTML source code currently shown on a display. Use this to inspect, modify or reuse existing content. Typical workflow: read_display_html to get the HTML, make changes, then send_html to push it back. Returns the complete HTML string plus metadata. If no live content is active, returns idle content if set. Requires content_only scope.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Ask business questions in plain English. Get instant answers from your database, no SQL needed.

  • Cloudflare Workers MCP server: code-explainer

  • Search FDA 510(k) clearances across all companies. Filter by company name (fuzzy match), product code, decision code (e.g., SESE=substantially equivalent), clearance type (Traditional, Special, Abbreviated), and date range. Returns clearance number (K-number), applicant, device name, decision date, and product code. Related: fda_device_class (product code details and classification), fda_product_code_lookup (cross-reference a product code across 510(k) and PMA), fda_search_pma (PMA approvals for higher-risk devices).
    Connector
  • Search FDA device recalls by recalling firm (fuzzy match), product code, recall status, or date range. Returns device-specific recall details including root cause, event type, and product codes. Complements fda_search_enforcement which covers all product types. Related: fda_search_enforcement (all recalls including drugs), fda_recall_facility_trace (trace to manufacturing facility), fda_device_class (product code details).
    Connector
  • Fetch HTTP response headers for a URL. Use when inspecting server configuration, security headers, or caching policies.
    Connector
  • Verify the email code and get a transfer token valid for 15 minutes. Call this after request_transfer_code and the user provides their code. Pass the returned transfer_token to get_transfer_code or unlock_domain. Args: order_id: The order ID of a completed domain purchase. code: The 6-digit code from the verification email.
    Connector
  • Returns trading aggregates per user: fill count, volume broken down by side, total fees (negative values represent net maker rebates), realized PnL, net funding paid or received, liquidation-fill count, distinct coins traded, and first/last trade timestamps. Omit `user` for leaderboard mode — returns a paginated list sorted by `sort_by`. Provide `user` for profile mode — returns a single row. Filters `coin` and `dex` compose additively — pass either or both to narrow the scope (`coin=BTC` for one market, `dex=xyz` for one venue, both together for redundancy). A mismatched combination (e.g. `coin=cash:TSLA&dex=xyz`) returns an empty result. Aggregation windows are fixed via the `interval` parameter — `1h`, `1d`, `1w`, `30d`, or omit for all-time. Data is refreshed hourly, so `1h` lags up to 1h. Vaults trade as normal accounts, so passing a vault address as `user` returns its trading performance — pair with `/v1/hyperliquid/vaults` for depositor-side stats. **Query Parameters:** - **user**: Filter by address<br>Single value or array of values* (separate multiple values with `,`)<br>*Plan restricted. - **interval**: Lookback window for user statistics (1 hour, 1 day, 1 week, 30 days). Omit for all-time. - **sort_by**: No description. - **coin**: Hyperliquid coin identifier. Core perps have no prefix (`BTC`, `HYPE`); spot pairs use `@N` (`@107`); builder DEXs prefix the symbol with the DEX name (`xyz:SILVER`).<br>Single value or array of values* (separate multiple values with `,`)<br>*Plan restricted. - **dex**: DEX identifier. `perps` for core perps, `spot` for `@N` spot pairs, or a builder DEX name (`xyz`, `cash`, …). Call `/v1/hyperliquid/dexes` for the live set.<br>Single value or array of values* (separate multiple values with `,`)<br>*Plan restricted. - **limit**: Number of items* returned in a single request.<br>*Plan restricted. - **page**: Page number to fetch.<br>Empty `data` array signifies end of results. **Responses:** - **200** (Success): Successful Response - Content-Type: `application/json` - **Response Properties:** - **request_time**: ISO 8601 datetime string - **Example:** ```json { "data": [ { "user": "string", "coin": "unknown_type", "dex": "unknown_type", "total_funding": 1.5, "volume_sold": 1.5, "transactions": 1, "realized_pnl": 1.5, "volume_bought": 1.5, "liquidation_fills": 1, "last_trade": "string", "interval": "unknown_type", "buys": 1, "total_volume": 1.5, "sells": 1, "first_trade": "string", "total_fees": 1.5, "coins_traded": 1 } ], "statistics": { "elapsed": 1.5, "rows_read": 1.5, "bytes_read": 1.5 }, "pagination": { "previous_page": 1, "current_page": 1 }, "request_time": "string", "duration_ms": 1.5, "results": 1.5 } ``` - **400**: Client side error - Content-Type: `application/json` - **Response Properties:** - **Example:** ```json { "status": "unknown_type", "code": "authentication_failed", "message": "string" } ``` - **401**: Authentication failed - Content-Type: `application/json` - **Response Properties:** - **Example:** ```json { "status": "unknown_type", "code": "authentication_failed", "message": "string" } ``` - **403**: Forbidden - Content-Type: `application/json` - **Response Properties:** - **Example:** ```json { "status": "unknown_type", "code": "authentication_failed", "message": "string" } ``` - **404**: Not found - Content-Type: `application/json` - **Response Properties:** - **Example:** ```json { "status": "unknown_type", "code": "authentication_failed", "message": "string" } ``` - **500**: Server side error - Content-Type: `application/json` - **Response Properties:** - **Example:** ```json { "status": "unknown_type", "code": "bad_database_response", "message": "string" } ```
    Connector
  • The unit tests (code examples) for HMR. Always call `learn-hmr-basics` and `view-hmr-core-sources` to learn the core functionality before calling this tool. These files are the unit tests for the HMR library, which demonstrate the best practices and common coding patterns of using the library. You should use this tool when you need to write some code using the HMR library (maybe for reactive programming or implementing some integration). The response is identical to the MCP resource with the same name. Only use it once and prefer this tool to that resource if you can choose.
    Connector
  • Returns the list of perpetuals DEXs and spot, each with 24h activity stats (volume, trade count, unique users, asset count). Hyperliquid hosts a core perpetuals venue (`dex=perps`) alongside builder-deployed perpetuals DEXs that each list their own asset universe — `xyz` (commodities and macro indices), `cash` (tokenized equities), `km`, and others. Use this endpoint to discover valid `dex` filter values for venue-scoped queries on `/markets`, `/markets/activity`, `/markets/liquidations`, `/users`, and `/users/positions`. For platform-wide totals across all DEXs over arbitrary intervals, use `/v1/hyperliquid/platform`. **Public — no auth required.** **Responses:** - **200** (Success): Successful Response - Content-Type: `application/json` - **Response Properties:** - **request_time**: ISO 8601 datetime string - **Example:** ```json { "data": [ { "dex": "perps", "assets": 1, "volume_24h": 1.5, "trades_24h": 1, "unique_users_24h": 1 } ], "statistics": { "elapsed": 1.5, "rows_read": 1.5, "bytes_read": 1.5 }, "pagination": { "previous_page": 1, "current_page": 1 }, "request_time": "string", "duration_ms": 1.5, "results": 1.5 } ``` - **400**: Client side error - Content-Type: `application/json` - **Response Properties:** - **Example:** ```json { "status": "unknown_type", "code": "authentication_failed", "message": "string" } ``` - **401**: Authentication failed - Content-Type: `application/json` - **Response Properties:** - **Example:** ```json { "status": "unknown_type", "code": "authentication_failed", "message": "string" } ``` - **403**: Forbidden - Content-Type: `application/json` - **Response Properties:** - **Example:** ```json { "status": "unknown_type", "code": "authentication_failed", "message": "string" } ``` - **404**: Not found - Content-Type: `application/json` - **Response Properties:** - **Example:** ```json { "status": "unknown_type", "code": "authentication_failed", "message": "string" } ``` - **500**: Server side error - Content-Type: `application/json` - **Response Properties:** - **Example:** ```json { "status": "unknown_type", "code": "bad_database_response", "message": "string" } ```
    Connector
  • Returns trading statistics per user: volume, PNL (realized, unrealized, total), trade counts, and activity window. When no user address is provided, returns a paginated leaderboard for discovery. Supports lookback windows via `interval`: `1h`, `1d`, `1w`, `30d`. Omit for all-time. Data refreshes hourly. **Query Parameters:** - **user**: undefined<br>Single value or array of values* (separate multiple values with `,`)<br>*Plan restricted. - **interval**: Lookback window for user statistics (1 hour, 1 day, 1 week, 30 days). Omit for all-time. - **sort_by**: No description. - **limit**: Number of items* returned in a single request.<br>*Plan restricted. - **page**: Page number to fetch.<br>Empty `data` array signifies end of results. **Responses:** - **200** (Success): Successful Response - Content-Type: `application/json` - **Response Properties:** - **request_time**: ISO 8601 datetime string - **Example:** ```json { "data": [ { "user": "string", "buys": 1.5, "sells": 1.5, "volume_sold": 1.5, "transactions": 1.5, "realized_pnl": 1.5, "volume_bought": 1.5, "unrealized_pnl": 1.5, "last_trade": "string", "total_pnl": 1.5, "total_volume": 1.5, "first_trade": "string" } ], "statistics": { "elapsed": 1.5, "rows_read": 1.5, "bytes_read": 1.5 }, "pagination": { "previous_page": 1, "current_page": 1 }, "request_time": "string", "duration_ms": 1.5, "results": 1.5 } ``` - **400**: Client side error - Content-Type: `application/json` - **Response Properties:** - **Example:** ```json { "status": "unknown_type", "code": "authentication_failed", "message": "string" } ``` - **401**: Authentication failed - Content-Type: `application/json` - **Response Properties:** - **Example:** ```json { "status": "unknown_type", "code": "authentication_failed", "message": "string" } ``` - **403**: Forbidden - Content-Type: `application/json` - **Response Properties:** - **Example:** ```json { "status": "unknown_type", "code": "authentication_failed", "message": "string" } ``` - **404**: Not found - Content-Type: `application/json` - **Response Properties:** - **Example:** ```json { "status": "unknown_type", "code": "authentication_failed", "message": "string" } ``` - **500**: Server side error - Content-Type: `application/json` - **Response Properties:** - **Example:** ```json { "status": "unknown_type", "code": "bad_database_response", "message": "string" } ```
    Connector
  • Answer questions using knowledge base (uploaded documents, handbooks, files). Use for QUESTIONS that need an answer synthesized from documents or messages. Returns an evidence pack with source citations, KG entities, and extracted numbers. Modes: - 'auto' (default): Smart routing — works for most questions - 'rag': Semantic search across documents & messages - 'entity': Entity-centric queries (e.g., 'Tell me about [entity]') - 'relationship': Two-entity queries (e.g., 'How is [entity A] related to [entity B]?') Examples: - 'What did we discuss about the budget?' → knowledge.query - 'Tell me about [entity]' → knowledge.query mode=entity - 'How is [A] related to [B]?' → knowledge.query mode=relationship NOT for finding/listing files, threads, or links — use workspace.search for that.
    Connector
  • Retrieves and queries up-to-date documentation and code examples from Context7 for any programming library or framework. You must call 'resolve-library-id' first to obtain the exact Context7-compatible library ID required to use this tool, UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query. IMPORTANT: Do not call this tool more than 3 times per question. If you cannot find what you need after 3 calls, use the best information you have.
    Connector
  • Propose compressing multiple related learnings into one consolidated learning. Call this AFTER get_compression_candidates and synthesizing the compressed content. Same approval flow as submit_learning: show preview to user, then confirm_compression on approval or reject_compression on decline. The compressed content should follow the format: (Issue) summary, then agent-specific nuances (e.g. grok adds X, claude adds Y).
    Connector
  • Generate a presentation from text content. Returns a generation_id to poll. Args: input_text: Content to transform into slides (text, markdown, or notes) title: Presentation title theme_id: Theme ID to use for the presentation. Call get_themes to discover available theme IDs and names for the authenticated user. vibe_id: Vibe ID for visual style. Call get_vibes to discover available vibes. Requires num_creative_variants >= 1 when set. slide_range: Target slides - 'auto', '1', '2-5', '6-10', '11-15', '16-20' additional_instructions: Extra guidance for the AI include_ai_images: Whether to generate AI images for slides num_creative_variants: Number of creative slide variants (0-2). Increases cost. image_ids: IDs of previously uploaded images to incorporate into slides. total_variants_per_slide: Number of distinct slide options to generate (1-4). export_formats: Output formats - 'link', 'pdf', 'ppt'. Defaults to ['link']. language: Output language, e.g. "French", "Japanese", "Spanish (Latin America)". If not set, matches the input language. Poll get_generation_status until status is 'completed'.
    Connector
  • Search for UK SIC 2007 codes by business activity description. Describe what a business does in plain English and get ranked SIC code recommendations with relevance scores, hierarchy breadcrumbs, and GICS/ICB cross-classification mappings. Useful for finding the right SIC code for Companies House registration.
    Connector
  • Search for UK SIC 2007 codes by business activity description. Describe what a business does in plain English and get ranked SIC code recommendations with relevance scores, hierarchy breadcrumbs, and GICS/ICB cross-classification mappings. Useful for finding the right SIC code for Companies House registration.
    Connector