nstbrowser-playwright-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NSTBROWSER_API_KEY | Yes | Your NSTBrowser API key | |
| NSTBROWSER_API_ADDRESS | No | NSTBrowser API endpoint | http://localhost:8848/api/v2 |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_sessionA | Create a browser session by connecting to an NSTBrowser profile via CDP. Provide profileId to connect to an existing profile, or call with no arguments to create a temporary one (all parameters are optional with sensible defaults). |
| list_sessionsA | List all active browser sessions |
| switch_sessionB | Switch the active browser session |
| close_sessionA | Close a browser session and disconnect from NSTBrowser |
| nst_get_profilesB | List available NSTBrowser profiles |
| nst_get_browsersB | List running NSTBrowser instances |
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 6 tools
The tools are mostly distinct: create/list/switch/close_session manage browser sessions, while nst_get_profiles and nst_get_browsers list profiles and running instances. There is some potential overlap between list_sessions and nst_get_browsers, but descriptions clarify sessions are CDP connections while browsers are NSTBrowser instances.
The session tools follow a consistent verb_noun pattern (create_session, list_sessions, switch_session, close_session). However, nst_get_profiles and nst_get_browsers deviate by using an 'nst_' prefix and 'get_' instead of 'list_', introducing a minor inconsistency.
A total of 6 tools is well-scoped for browser session management. Each tool serves a clear purpose without redundancy, and the count is well within the ideal range for a focused server.
The tool set covers the full session lifecycle (create, list, switch, close) plus the necessary discovery operations for profiles and running browsers. There are no obvious gaps for the stated domain of managing NSTBrowser connections.