Steel MCP Server
Related Servers
Alternatives to Steel MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables MCP clients to drive a real, logged-in Chrome browser for web automation tasks like navigation, clicking, typing, and screenshotting.2 npmMIT
- AlicenseBqualityCmaintenanceEnables MCP clients to drive a real Chromium browser for automation, including navigation, JavaScript execution, CDP commands, network capture, and multi-tab control.737 PyPIGPL 3.0
- AlicenseAqualityAmaintenanceEnables MCP clients to drive a self-hosted Chrome session for browsing tasks through browser tools, while providing a live view URL so a human can take over at prompts like logins or 2FA.914Apache 2.0
- FlicenseNot gradedqualityDmaintenanceDrive your real, signed-in Chrome browser from any MCP client, enabling browser automation such as navigation, clicking, typing, and screenshots through standard MCP tools.1-
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to control and interact with the user's real Chrome browser session, leveraging existing logins, cookies, and extensions for AI-driven automation.5MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents and human operators to drive isolated browser profiles with persistent cookies, fingerprints, and proxies, exposing navigation, clicking, typing, extraction, screenshots, JS evaluation, tabs, cookies, and waits to MCP clients.-
TDQS
Scored across 16 tools
Most tools have clearly distinct roles, and the descriptions are unusually explicit about which read, act, or session-management tool to use. The only mild confusion is among session_live_view, session_diagnostics, and session_replay, but their definitions separate active viewing, activity inspection, and replay.
All tools share the steel_ prefix and consistent snake_case, and most follow an action-oriented style like scrape, navigate, find, act, and wait_for. A few noun-style names such as session_live_view, session_options, and session_diagnostics deviate slightly from the dominant verb_noun pattern, but the overall scheme remains predictable.
Sixteen tools is slightly above the typical well-scoped range, but the browser-automation domain legitimately needs separate read, act, session-lifecycle, and diagnostic tools. Each tool appears to earn its place rather than duplicating another.
The toolset covers the full browser-automation lifecycle: non-session reads, session creation and release, navigation, element discovery, acting, waiting, diagnostics, human handoff, replay, and batch execution. There are no obvious dead ends; the surface supports both lightweight scraping and complex interactive sessions.