mcp-rnw-browser
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rnw_navigateA | Navigate to a URL in the browser. Creates a browser session if none exists. |
| rnw_snapshotA | Get a text snapshot of interactive elements on the page. Returns element positions that can be used for clicking. |
| rnw_screenshotB | Take a screenshot of the current page or a specific element. Returns a base64-encoded PNG image that can be viewed by AI agents. |
| rnw_clickA | Click on an element using React Native Web compatible mouse events. Can find element by CSS selector, text content, testID, or exact coordinates. |
| rnw_typeB | Type text into a focused element or find an element and type into it |
| rnw_scrollB | Scroll the page or a specific element |
| rnw_waitC | Wait for a specified time or for an element to appear |
| rnw_press_keyC | Press a keyboard key |
| rnw_evaluateB | Execute JavaScript in the browser context. Useful for advanced interactions or debugging. |
| rnw_tabs_listA | List all open browser tabs with their index and URL |
| rnw_tabs_newB | Create a new browser tab and optionally navigate to a URL |
| rnw_tabs_selectC | Switch to a specific browser tab by index (0-based) |
| rnw_tabs_closeB | Close a browser tab by index. If no index provided, closes the current tab. |
| rnw_session_statusA | Get the current browser session status including whether browser is running, number of tabs, current tab info, and viewport size. |
| rnw_closeB | Close the browser and end the session |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Each tool maps to a distinct browser action or session/tab operation. Snapshot vs screenshot and evaluate vs click/type are clearly differentiated by their descriptions. No two tools appear to do the same thing.
All tools share the rnw_ prefix and snake_case, which makes them readable and groupable. However, the internal pattern is not uniformly verb_noun (e.g., rnw_tabs_list, rnw_session_status vs rnw_navigate, rnw_click), so there are minor deviations.
15 tools for a browser automation server is well within the useful range. Each tool covers a necessary primitive: navigation, inspection, interaction, tab management, and session lifecycle. No obvious redundancy.
Core browser automation lifecycle is covered, including navigation, interaction, tab management, and session teardown. Advanced interactions like hover, drag, file upload, iframe handling, or network interception are absent, but agents can work around many via rnw_evaluate.