termux-puppeteer-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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_sessionA | Create a new browser session for multi-step workflows. Returns a sessionId that persists state between calls. Sessions auto-expire after 5 minutes of inactivity. |
| close_sessionA | Close a browser session and free up resources. Sessions auto-close after timeout, but explicit closing is recommended. |
| list_sessionsA | List all active browser sessions with their status |
| puppeteer_navigateA | Navigate to a URL and get the page content/title. If sessionId provided, uses existing session. Otherwise creates a temporary session. |
| puppeteer_clickC | Click an element on the current page. Requires sessionId to maintain state after navigation. |
| puppeteer_screenshotB | Take a screenshot of the current page state and return as base64 JPEG. If sessionId provided, screenshots the current state. Otherwise navigates to URL first. |
| puppeteer_screenshot_debugA | Take a screenshot and save it to a file, then open with termux-open for debugging. Works with sessionId to capture current state. |
| puppeteer_evaluateB | Execute JavaScript in the page context and return the result. Requires sessionId. |
| get_page_contentB | Get the HTML content of the current page. Requires sessionId. |
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 9 tools
Most tools are distinct, but puppeteer_screenshot and puppeteer_screenshot_debug overlap in purpose (both take screenshots), and get_page_content and puppeteer_navigate both return page content. This could cause confusion for an agent.
Naming is inconsistent: some tools use verb_noun snake_case (close_session, create_session), while others use a 'puppeteer_' prefix with lowercase verb (puppeteer_click, puppeteer_navigate). This mixed pattern reduces predictability.
9 tools is well-scoped for a browser automation server, covering essential session management and page interaction actions without excess.
Basic operations are covered (navigate, click, evaluate, screenshot, get content), but common actions like form filling and element waiting are missing, leaving notable gaps for complex workflows.