pinchtab-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
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 |
|---|---|
| pinchtab_list_instancesA | List all open browser tabs. Returns tab IDs, URLs, and titles. |
| pinchtab_close_tabB | Close the current tab or a specific tab by its ID. |
| pinchtab_cookiesA | Get all cookies for the current page. |
| pinchtab_healthA | Check if PinchTab server is running and responsive. |
| pinchtab_navigateA | Navigate the browser to a URL. Set waitMs to wait for page load and get a snapshot back automatically. |
| pinchtab_snapshotA | Get an accessibility tree snapshot of the page. Returns element refs (e0, e1, …) that can be used with click/type/press. Use filter='interactive' for fewer tokens. Use format='compact' for minimal output. |
| pinchtab_scrollA | Scroll the page or a specific element. Supports all four directions. |
| pinchtab_waitA | Wait for a specified number of seconds. Useful after navigation or dynamic content loading. |
| pinchtab_wait_for_selectorA | Wait for a CSS selector to appear on the page. Polls every 500ms up to the timeout. Useful for waiting on dynamic content, modals, or lazy-loaded elements. |
| pinchtab_clickA | Click an element by its ref ID (e.g. 'e5'). Uses human-like click by default. Set waitMs to get a snapshot after clicking (saves a round-trip). For SPAs, clicking may not cause full navigation. |
| pinchtab_typeA | Type text into an input field by its ref ID. Uses human-like typing by default. Set clearFirst=true to click, select all, then type — required for React/Vue/Angular inputs where direct fill doesn't trigger state updates. |
| pinchtab_pressC | Press a keyboard key (e.g. 'Enter', 'Tab', 'Escape', 'ArrowDown'). Optionally target a specific element. |
| pinchtab_hoverA | Hover over an element by its ref ID. Triggers mouseover/mouseenter events — useful for revealing tooltips, dropdown menus, or hover states. |
| pinchtab_focusA | Focus an element by its ref ID. Useful for triggering focus-dependent UI (e.g. autocomplete dropdowns) without clicking. |
| pinchtab_selectA | Select an option in a dropdown by its ref ID. Pass the option value or visible text. |
| pinchtab_get_textA | Get readable text content from the page (~800 tokens). Best for extracting article content or page information. |
| pinchtab_screenshotB | Take a screenshot of the page. Returns a base64-encoded image. |
| pinchtab_evalB | Execute JavaScript code in the page context. Returns the result of the expression. |
| pinchtab_pdfA | Export the current page as a PDF. Returns the PDF as base64. |
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 19 tools
Each tool targets a distinct browser automation action (click, type, scroll, navigate, etc.) with no functional overlap. Even similar actions like click vs focus vs hover are clearly differentiated by their descriptions and use cases.
All tools use the pinchtab_ prefix and snake_case. However, there is a minor inconsistency: some tools use verb_noun (e.g., pinchtab_list_instances, pinchtab_get_text) while others are just a noun (e.g., pinchtab_cookies, pinchtab_screenshot) instead of pinchtab_get_cookies or pinchtab_take_screenshot.
19 tools cover the essential browser automation operations without being excessive. Each tool serves a clear purpose, and the number feels well-scoped for a comprehensive automation server.
The tool set covers most common browser interactions: navigation, input, events, screenshots, PDF, cookies, evaluation, and tab management. Missing features like file upload or drag-and-drop are minor gaps that can be worked around with eval.