Skip to main content
Glama
Stellarhold170NT

Steel MCP Server

by Stellarhold170NT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Steel MCP Server

No user-submitted related servers found.

    Related Servers

    • monkeysee

      juliocesar
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP clients to drive a real, logged-in Chrome browser for web automation tasks like navigation, clicking, typing, and screenshotting.
      0
      1
      MIT

    • chrome-mcp

      xiyiyiru
      A
      license
      B
      quality
      C
      maintenance
      Enables MCP clients to drive a real Chromium browser for automation, including navigation, JavaScript execution, CDP commands, network capture, and multi-tab control.
      7
      GPL 3.0

    • chrome-mcp

      dawei008
      F
      license
      Not graded
      quality
      D
      maintenance
      Drive 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
      -

    • Browser MCP

      CypherPotato
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP clients to control a real local browser window for web automation tasks such as clicking, typing, scrolling, and taking screenshots.
      9 npm
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 16 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources