Skip to main content
Glama
260,211 tools. Last updated 2026-07-05 05:07

"How to send Chrome network and console logs to Cursor editor" matching MCP tools:

  • MONITORING: Fetch Terraform deployment logs with pagination Fetches logs from a running or completed Terraform deployment job. For **completed jobs**: uses REST endpoint for instant retrieval (supports `tail` for server-side filtering). For **running jobs**: streams via SSE with timeout-based pagination. **PAGINATION** (running jobs only): Use `last_event_id` from the response to fetch more: 1. First call: `tflogs(session_id='...')` → get logs + `last_event_id` 2. Next call: `tflogs(session_id='...', last_event_id='...')` → get NEW logs only 3. Repeat until `complete: true` in response **RESPONSE FIELDS**: - `logs`: Array of log messages collected - `last_event_id`: Pass this back to get more logs (pagination cursor, SSE only) - `complete`: true if job finished, false if more logs may be available - `total_logs`: total log entries before tail truncation REQUIRES: session_id from convoopen response (format: sess_v2_...). OPTIONAL: job_id to target a specific deployment (use tfruns to discover IDs), timeout (default 50s, max 55s), last_event_id (for pagination), tail (return only last N entries) ⚠️ CONTEXT WARNING: Deploy logs can be hundreds of lines. Use tail: 50 for completed jobs to avoid blowing up the context window.
    Connector
  • Context lookup: Parse a User-Agent header string into structured browser, OS, device type, and rendering-engine components. Use to identify client capabilities from a raw UA string, e.g. when analysing server logs or request headers; does not perform any network lookups — entirely local parsing. Runs synchronously using the ua-parser-js library with no external calls. Returns a JSON object with browser.name, browser.version, os.name, os.version, device.type, device.vendor, and engine.name fields; unknown fields are empty strings.
    Connector
  • Curated roster of the AI platforms + agent frameworks in the DC Hub agent ecosystem — each with its recommended DC Hub tools and authentication tier. Recognized MCP clients include Claude and Cursor, with Cline, Continue and other agents surfaced as they are integrated. Use it to see which platforms DC Hub supports and how to connect them. Try: get_agent_registry. NOTE: this is a curated ecosystem/capability index, NOT live per-caller call/citation telemetry. Do NOT use for platform uptime / backup health (use get_backup_status).
    Connector
  • Curated roster of the AI platforms + agent frameworks in the DC Hub agent ecosystem — each with its recommended DC Hub tools and authentication tier. Recognized MCP clients include Claude and Cursor, with Cline, Continue and other agents surfaced as they are integrated. Use it to see which platforms DC Hub supports and how to connect them. Try: get_agent_registry. NOTE: this is a curated ecosystem/capability index, NOT live per-caller call/citation telemetry. Do NOT use for platform uptime / backup health (use get_backup_status).
    Connector
  • Returns a structured snapshot of the LMCP environment: server/tray/teams-proxy versions, detected AI client, cloud relay state, TCC permission states (Calendar/Reminders/Contacts), and a compact summary of which services (Mail/Calendar/Contacts/Teams/OneDrive/Reminders/Notes) are reachable. Fast (<500ms), passive — never prompts the user, never opens app windows, never touches the network. Call this when you need to verify the environment is healthy before attempting a tool, or to understand what's installed and accessible. For reporting failures, use `report_problem` instead — it captures this same snapshot plus logs and submits to the team.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Transform any blog post or article URL into ready-to-post social media content for Twitter/X threads, LinkedIn posts, Instagram captions, Facebook posts, and email newsletters. Pay-per-event: $0.07 for all 5 platforms, $0.03 for single platform.

  • Render HTML and CSS to PNG images over HTTP. Send HTML and CSS and get a PNG back.

  • Upload a file (base64) and attach it to a page (editor+) — an image, PDF, dataset, etc. Returns the serve URL plus a ready-to-paste `markdown` snippet; then call update_page or patch_page to place it in the body (images render inline as ![](…), other files as a download card). The payload is inline base64 and rides through the model's context, so it is capped at 5 MB — keep it to small files (screenshots, charts, short PDFs). For larger files use request_attachment_upload (a direct PUT URL, bytes off-context), or the tela editor (drag-drop).
    Connector
  • Post a question to the network. Other agents can answer and earn USDC. Broadcast (default): question visible to all agents via browse_qa(). Directed: pass agent_id + playbook_id to send privately to one agent — only they see it in their inbox, never in broadcast browse_qa(). playbook_id is required when agent_id is set. Args: api_key: Your API key question: Your question (max 2000 chars) tags: Comma-separated tags for discoverability (broadcast only) agent_id: Optional — direct this question to a specific agent playbook_id: Required when agent_id is set — playbook the question is about
    Connector
  • Interleaved cross-org release feed for a collection — same shape as `get_latest_releases` but scoped to the collection's member orgs. Cursor-paginated: pass `limit` for slice size (default 20), `cursor` to continue from a prior call. The result's `_meta.pagination` carries `kind: 'cursor'`, `hasMore`, and `nextCursor` when more rows exist; the response text echoes `nextCursor` so an LLM caller can chain without parsing `_meta`. Cursors are stable under inserts.
    Connector
  • List all active sellers on the Kifly network. **Requires a network token (kfn_live_…).** Returns each seller's handle, name, city, region, delivery coverage (`nationwide:true` or a `states` list), delivery fee, and catalog size. `delivery_coverage.cities` may be capped to a handful of entries — compare `cities.length` against `city_count`; if fewer, call `get_seller` for that seller's full city list. Use this to discover which sellers are available and which ship to a buyer's location before calling `get_seller` or `search_products`. **Pagination:** when `kifly:hasMore` is true, pass `kifly:nextCursor` as `cursor` to fetch the next page. Default page size is 20, max 50.
    Connector
  • List all active sellers on the Kifly network. **Requires a network token (kfn_live_…).** Returns each seller's handle, name, city, region, delivery coverage (`nationwide:true` or a `states` list), delivery fee, and catalog size. `delivery_coverage.cities` may be capped to a handful of entries — compare `cities.length` against `city_count`; if fewer, call `get_seller` for that seller's full city list. Use this to discover which sellers are available and which ship to a buyer's location before calling `get_seller` or `search_products`. **Pagination:** when `kifly:hasMore` is true, pass `kifly:nextCursor` as `cursor` to fetch the next page. Default page size is 20, max 50.
    Connector
  • Get build and runtime logs for a deployment. If no deployment_id is provided, returns logs for the latest deployment. Use this after calling deploy to monitor build progress and diagnose failures. Logs include: framework detection output, dependency installation, build steps, container startup, and health check results. If a deployment fails, check the logs for error details — common issues include missing dependencies, build errors, or the app not listening on the correct PORT (check the PORT env var — 8080 for auto-detected frameworks, or the EXPOSE value from Dockerfile).
    Connector
  • Full detail of a single Editor Digest — title, standfirst, full HTML body, FAQ, sentiment, and tickers. Pass the editor slug and a digest date (YYYY-MM-DD) or slug; omit the date to get that editor's latest published digest. Use get_digests to discover editors + dates.
    Connector
  • The Agora's one paid action: pay tiny x402 postage to DELIVER a PRIVATE direct message into another agent's inbox. Everything conversational is FREE (browse, post, reply in public threads, read your inbox); you pay only for private, targeted reach (the postage is what makes a private message get read, not spam-filtered). If a public answer works, use the free aicom_agora_reply instead. This returns the QUOTE only (price, asset, network, how to send); to actually send, GET /agora/message for a nonce then POST /agora/message with {nonce, signal_id|to, body}.
    Connector
  • SKILL: how_to_send_lnt_email Team: platform How to Send an L&T Branded Email Call this tool to get the complete guide for 'how_to_send_lnt_email'. Read the 'content' field and follow its instructions. This tool takes NO parameters. Full content: --- name: how_to_send_lnt_email description: Instructions for sending L&T branded emails — explains exactly what steps to follow and which tools to call --- # How to Send an L&T Branded Email Follow these exact steps whenever a user wants to send any information by email. ## When to Use This Guide - User says "send this to [email]" - User says "email this to [name]" - User says "mail the results to..." - User wants to share any data or information via email ## Step 1 — Collect These 5 Things Ask the user for anything missing: 1. **Recipient email address** — where to send 2. **Recipient name** — for the greeting "Dear [name]," 3. **Sender name** — for the signature "Warm regards, [name]" 4. **Subject line** — or derive it from the content 5. **Email content** — what to put in the body Do not proceed until you have all 5. ## Step 2 — Read the Brand Guidelines Call the `lnt_email_brand_guidelines` tool (no arguments needed). Read the returned content carefully. Use those guidelines to generate the complete HTML email yourself. Build the HTML with: - Navy header + orange accent bar - "Dear [recipient name]," - Body content formatted as paragraphs or table - "Warm regards, [sender name]" signature - Gray footer with confidential notice ## Step 3 — Send the Email Call the `send_email` tool with this exact JSON: ```json { "personalizations": [ { "to": [{"email": "RECIPIENT_EMAIL_HERE"}], "subject": "SUBJECT_HERE" } ], "from": {"email": "lntcs@lntecc.com"}, "content": [ { "type": "text/html", "value": "YOUR_GENERATED_HTML_HERE" } ] } Step 4 — Confirm to User On success: "✅ Email sent to [name] at [email]." On failure: "❌ Could not send. Error: [message]." Important Rules NEVER call lnt_email_brand_guidelines with arguments — it takes none NEVER send plain text — always generate and send HTML From address is ALWAYS lntcs@lntecc.com — never change this Generate the HTML yourself — do not look for an HTML generation tool Subject must be specific and descriptive
    Connector
  • [Runtime] Snapshot of the Docker container logs produced by an OctoPerf load test — the same lines the web UI streams on the running-bench logs panel. Use this to diagnose launch failures (image pull errors, provider quotas, missing project files, agent boot crashes) when `get_bench_result` reports `state=ERROR` or the run is stuck in PREPARING / INITIALIZING. Returns one entry per log line with `date`, `level` (INFO / WARN / ERROR), and `message`. The server resolves the BenchResult's batchId internally — pass the `benchResultId`, not the batchId. No incremental cursor; the upstream API always returns the full log set, sort/filter client-side.
    Connector
  • Find the right network or chain name to use across EVM, Solana, Bitcoin, Substrate, and Hyperliquid. COMMON USER ASKS: - Find Base-like networks - Show Solana mainnets - Show Substrate mainnets FIRST CHOICE FOR: - finding the correct network before any other query WHEN TO USE: - You are not sure which network name, chain name, or alias to use. - You want to filter networks by VM family, network type, or real-time availability. DON'T USE: - You already know the exact network and want live data from that network. EXAMPLES: - Find Base-like networks: {"query":"base","limit":10} - Show Solana mainnets: {"vm":"solana","network_type":"mainnet"} - Show Substrate mainnets: {"vm":"substrate","network_type":"mainnet"}
    Connector
  • Reads the rendered text content of a Google Chrome tab. Identify the tab either by `url_match` (substring match against URL; first hit wins) or by `window_index` + `tab_index` (from chrome_list_tabs). Text is capped at `max_bytes` (default 100 KB). Pass `include_html: true` to also get the raw HTML source. Pass `include_links: true` to extract all links with their href and text. Requires 'Allow JavaScript from Apple Events' (Chrome → View → Developer); run chrome_setup_check if reads come back empty.
    Connector
  • Send a contact message to a broker on Venturu by their profile slug. Requires an authenticated Venturu account. Set inquiryType to "buying" (default) for buyer representation or "selling" for seller representation. Provide the broker slug and the message to send. Use search_brokers to find broker slugs.
    Connector
  • Send a contact message to a broker on Venturu by their profile slug. Requires an authenticated Venturu account. Set inquiryType to "buying" (default) for buyer representation or "selling" for seller representation. Provide the broker slug and the message to send. Use search_brokers to find broker slugs.
    Connector