Typora MCP
Related Servers
Alternatives to Typora MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables snapshot-driven browser automation through a stdio MCP interface: navigate pages, capture accessibility snapshots, and act on elements by snapshot references, including clicking, typing, filling forms, managing tabs, and reading console or network activity.80 npmMIT
- AlicenseNot gradedqualityDmaintenanceConnects local stdio MCP servers to an existing Chrome 144+ session, preserving the user's signed-in sessions, cookies, tabs, and extension environment without launching a second browser. It provides tab control, semantic snapshots, screenshots, pointer, keyboard, form selection, scrolling, navigation, and waiting tools.MIT
- AlicenseNot gradedqualityDmaintenanceConnects to Obsidian's Electron process via Chrome DevTools Protocol, enabling AI assistants to screenshot, execute JavaScript, capture console logs, and automate UI actions for debugging plugins and testing layouts.ISC
- AlicenseNot gradedqualityBmaintenanceEnables debugging web pages in Chrome through a stdio MCP interface, including performance traces, network and console inspection, snapshots, screenshots, emulation, and page input by element UID.79 npmMIT
- AlicenseNot gradedqualityBmaintenanceExposes browser tabs to any MCP client through a local broker, letting agents discover pages, take text snapshots with numbered elements, and drive them via click, type, navigate, eval, network/log inspection, and screenshots. Supports stdio, Streamable HTTP, and SSE transports so IDE and CLI agents can orchestrate browser automation.MIT
- AlicenseDqualityBmaintenanceConnects to an already-running Chrome/Chromium instance over CDP and exposes 75 browser-automation tools over newline-delimited MCP JSON-RPC on stdin/stdout, covering navigation, forms, keyboard/mouse input, screenshots, cookies, storage, tabs and frames, assertions, and retry/batch/step composition. It does not launch a browser itself, requiring a localhost debugging port on the existing instance.75MIT
TDQS
Scored across 28 tools
Most tools target clearly distinct purposes (lifecycle, bridge management, debug capture, interaction). There is mild overlap among the DOM-reading group (get_dom, typora_snapshot, query_selector, get_element), but descriptions explicitly steer between them (snapshot preferred over full HTML), so an agent can disambiguate.
Nearly all tools follow a verb_noun convention, which is readable and predictable. The main deviation is the inconsistent presence of the typora_ prefix: some tools are prefixed (typora_status, typora_launch) while others are bare (get_dom, click, type), so the namespace is split across two styles.
At 28 tools this is on the heavy side for a single-application automation server. The surface is defensible given the breadth (process control, bridge, DOM, CDP, debug, interaction), but several tools could plausibly be consolidated, pushing it above the well-scoped 3-15 range.
Coverage spans process lifecycle, bridge install/uninstall, document opening, source reading, DOM inspection, CDP, debug event capture, and user interactions like click/type/scroll/screenshot. Gaps exist (no explicit document save or new-document creation), but core workflows are well covered.