browser-console-mcp-tools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_console_messagesB | Get browser console messages. Filter by type (error, warn, log, info, debug) and limit the number of messages returned. |
| get_console_errorsA | Get only error messages from the browser console. Returns detailed error information including stack traces. |
| clear_console_messagesB | Clear all stored console messages. |
| get_console_statsB | Get statistics about console messages (counts by type, recent activity). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| All Console Messages | All captured console messages from the browser |
| Console Errors | Only error messages from the browser console |
| Console Statistics | Statistics about captured console messages |
TDQS
Scored across 4 tools
get_console_messages and get_console_errors overlap since errors are a subset of messages filterable by type='error', but the errors tool adds distinct value (stack traces, detailed error info), so the boundary is defensible. clear_console_messages and get_console_stats are clearly distinct.
All four tools follow a consistent snake_case verb_noun pattern (get_, get_, clear_, get_). The convention is predictable and readable throughout.
Four tools is well-scoped for a browser console inspection purpose: two retrieval variants, one clear, one stats. Each earns its place with no bloat.
Read, filtered read, clear, and stats cover the core console lifecycle. Minor gap: no way to wait/subscribe for new messages or export logs, but agents can poll existing tools to work around this.