Zypin MCP
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| navigateC | Navigate to a URL |
| go_backB | Go back to the previous page |
| go_forwardB | Go forward to the next page |
| reloadB | Reload the current page |
| clickC | Click an element on the page |
| typeC | Type text into an input field |
| selectC | Select an option from a dropdown |
| fill_formC | Fill multiple form fields at once |
| snapshotB | Get a snapshot of the current page with interactive elements |
| screenshotC | Take a screenshot of the current page |
| get_textC | Get text content from an element |
| get_urlB | Get the current page URL |
| get_titleB | Get the current page title |
| wait_forC | Wait for an element to appear on the page |
| evaluateC | Run JavaScript code on the page |
| closeB | Close the browser |
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 16 tools
Most tools have clearly distinct purposes for browser automation tasks, with minimal overlap. However, 'snapshot' and 'screenshot' could potentially be confused as both capture page states, though their descriptions differentiate them (screenshot is visual, snapshot includes interactive elements).
All tool names follow a consistent snake_case pattern with clear verb-action naming (e.g., 'click', 'navigate', 'get_text'). The naming convention is uniform throughout the set, making it easy to understand each tool's purpose at a glance.
16 tools is well-scoped for a browser automation server, covering essential navigation, interaction, data extraction, and page state operations. Each tool serves a distinct purpose that earns its place in the set without feeling excessive or insufficient.
The toolset provides comprehensive coverage for core browser automation tasks including navigation, interaction, form handling, and page inspection. Minor gaps exist, such as no explicit tool for handling cookies, managing windows/tabs, or executing more complex user interactions like drag-and-drop, but agents can work around these with existing tools.