io.github.morfiade-app/morfiade-mcp
OfficialRelated Servers
Alternatives to io.github.morfiade-app/morfiade-mcp
- FlicenseDqualityDmaintenanceProvides direct access to Chrome DevTools Protocol for browser automation, enabling navigation, screenshot capture, and execution of any CDP command for flexible browser control.42-
- FlicenseAqualityAmaintenanceEnables AI agents to manage multiple Google accounts with persistent sessions and anti-detect browser fingerprints, supporting sign-in, account switching, Gmail access, and interaction with any Google SSO website.42-
- AlicenseAqualityAmaintenanceMCP server + Chrome extension that drive the user's real, logged-in Chrome over a local WebSocket. 59 token-efficient web-dev tools: compact element refs instead of screenshots, server-side table filtering, visual regression, accessibility/SEO/security audits, network mocking. Also runs on ChromeOS/Crostini.691,144 npm7MIT
- AlicenseBqualityDmaintenanceMCP server that attaches to already-running Chromium browsers via CDP, enabling agents to control multiple browser sessions for navigation, input, network capture, and automation while avoiding anti-bot detection with Patchright.261MIT
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage GPMLogin browser profiles over the GPM Local API — health checks, listing and searching profiles, creating profiles with proxy aliases, renaming, starting and stopping, and approval-gated deletion. It supports both gpm-v3 and global-v1 API flavors, stores proxy credentials in Windows Credential Manager, and defaults to read-only mode so writes and deletes must be explicitly enabled and approved.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to control local Chrome/Edge browser profiles through MCP, including tab groups, bounded DOM actions, observations, and optional encrypted credential use.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to control an existing signed-in Chrome profile through MCP stdio, using its current tabs, cookies, and logins without pairing or a separate browser. It exposes tab management, page interaction, screenshots, and Chrome DevTools Protocol commands.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to drive isolated local browser profiles, each with its own persistent cookies, login state, fingerprint, and proxy, so authenticated workflows carry across sessions. Exposes tools for navigation, clicking, typing, extraction, screenshots, JS evaluation, tab and cookie management, and raw CDP commands to any MCP client.MIT
- FlicenseNot gradedqualityAmaintenanceExposes a local MCP endpoint that lets AI agents and human operators drive isolated Chromium profiles — each with its own cookies, fingerprint, and proxy — through tools for navigation, clicking, typing, extraction, screenshots, JS evaluation, tabs, and cookie management. Persistent per-profile session state keeps logins and context alive across launches and across AI sessions, so agents can complete real authenticated workflows.-
- AlicenseAqualityBmaintenanceEnables AI assistants to drive a locally installed Google Chrome window with human-like navigation, page inspection, clicking, typing, dragging, scrolling, tab management, and screenshots, while sharing one persistent browser session across sessions.13MIT
TDQS
Scored across 18 tools
Each tool targets a distinct resource and action: profile lifecycle, proxy testing, metadata, and the four sync tools are clearly separated by their descriptions. The only real overlap is check_proxy/check_proxies, which is explicitly resolved by the description directing multi-profile use to the plural form. profile_note and profile_tags share a read/write interface but operate on clearly different fields.
The dominant pattern is snake_case verb_noun (create_profile, stop_profile, check_proxy, list_profiles), and the sync_* group is internally consistent. Deviations include status as a bare noun and profile_tags/profile_note, which invert the convention by leading with the resource. Overall the set is readable and predictable despite these minor inconsistencies.
18 tools is slightly above the ideal 3-15 range, but the server covers three distinct subdomains—profile lifecycle, proxy management, and window sync—each of which justifies its tools. The four sync tools alone form a complete pipeline that would be impossible to compress without losing clarity. It feels slightly heavy but not bloated.
The domain is well covered: full profile lifecycle (create, list, start, stop, trash, restore), proxy set/test/clear, and a complete sync workflow (windows, sets, spread, insert) with no obvious dead ends. Minor gaps exist—profile category cannot be updated after creation, trash cannot be emptied, and hard deletion is unavailable—but these appear to be intentional policy limits rather than oversights.