Skip to main content
Glama
458,314 tools. Updated 2026-08-16 06:47

"How to check console logs and network activity" matching MCP tools:

  • Fetch recent Unity console logs filtered by level, keyword, or time range. Inspect runtime messages, warnings, and errors to diagnose issues; compile errors are handled separately.
    MIT
  • Retrieve recent RawTree query and insert logs to troubleshoot errors, verify activity, and inspect SQL with filters by type, status, origin, and table.
    MIT
  • Create a console watermark that records the current timestamp. Use the returned mark ID to fetch only logs generated after that moment.
    MIT
  • Retrieve browser console logs from Webvizio tasks when the task prompt lacks sufficient information for execution, providing additional context to complete development tasks.
    MIT

Matching MCP Servers

  • A
    license
    -
    quality
    C
    maintenance
    A minimal MCP server with get_weather and create_ticket tools, used for testing MCP servers across protocol, unit, eval, transport, and auth layers.
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    Enables validation of commit messages, branch names, author info, push safety, and repository state using commit-check rules, accessible as MCP tools.
    8
    MIT

Matching MCP Connectors

  • Retrieve full details of a resource by ID, including files, workflows, agents, and activity logs.
    MIT
  • Retrieve blockchain event logs by specifying network, contract addresses, and topic filters. Access detailed on-chain activity data for analysis and monitoring purposes.
    MIT
  • Clear console, JS errors, and network logs to reset browser state before navigating to a new page, ensuring fresh data in subsequent inspections.
    MIT
  • Extract specific failing network, console, mutation, interaction, or navigation events from a recorded browser session using category filters to surgically isolate errors without overwhelming your context.
    MIT
  • Collect a full debugging snapshot of the browser: current URL, title, console logs, alerts, and network requests with headers/body. Filter by URL, method, or console type to pinpoint issues.
    MIT
  • Retrieve recent events from the unified buffer of server stdout/stderr and browser console/network/pageerror. Filter by source, stream, or regex, and tail incrementally since a sequence number.
    MIT
  • Retrieve browser console messages (log, warn, error) to debug JavaScript errors and inspect application logs. Filter by level or clear the buffer after reading.
    MIT
  • Retrieve the recorded timeline of the active pair-debugging session, including console logs, network requests, errors, navigations, and actions. Use this to diagnose issues when something appears wrong.
    MIT
  • List buffered console logs from the current page with optional level and time filters, and group by message, source, or severity.
    MIT
  • Fetch the full detail for a bug report by ID—description, console logs, network requests, screenshot, classification, and fix history. Use when you need the complete record.
    MIT