A
licenseC
qualityD
maintenanceEnables LLMs to perform web browsing tasks, take screenshots, and execute JavaScript using Puppeteer for browser automation.
4
29,827 npm
1
MIT
Steel MCP Server
by steel-dev
Related Servers
Alternatives to Steel MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to perform browser automation including web navigation, element interaction, and screenshot capture using Puppeteer. It provides capabilities for executing JavaScript in the browser and monitoring console logs for debugging and data extraction.29,827 npmMIT
- AlicenseBqualityDmaintenanceEnables AI agents to automate browser interactions including navigation, content extraction, form filling, screenshots, and JavaScript execution across multiple tabs using Puppeteer.2722 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to open URLs in a persistent headless browser and interact with pages by clicking, typing, selecting, reading content, evaluating JavaScript, waiting for elements, and capturing screenshots.22 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to control a browser through tools for navigation, typing, clicking, and taking screenshots to perform web automation tasks.Apache 2.0
- AlicenseBqualityBmaintenanceEnables LLMs to interact with web pages, take screenshots, and execute JavaScript in a real browser environment10462 npm297MIT
TDQS
A3.5/5.0
Scored across 16 tools
Disambiguation4/5
Most tools have clearly distinct purposes, with stateless reading (scrape, screenshot, pdf) separated from session interaction (navigate, act, snapshot). A few pairs like steel_screenshot/steel_snapshot and steel_session_live_view/steel_session_replay have similar names, but detailed descriptions resolve the boundaries.
Naming Consistency4/5
All tools share the steel_ prefix and snake_case, but the pattern mixes bare verbs (scrape, navigate, act) with session_ prefixed noun_verb forms (session_create, session_release, session_handoff). This is consistent enough to be predictable, with minor deviations like steel_pdf and steel_wait_for.
Tool Count4/5
16 tools is slightly above the typical 3-15 range, but the breadth covers stateless captures, session lifecycle, element targeting, and diagnostics. Each tool addresses a distinct need, so the count feels justified rather than bloated.
Completeness4/5
The surface covers the core browser automation lifecycle: create/release sessions, navigate, read, interact, wait, and diagnose. Obvious gaps include a full-HTML/markdown read within a live session and session-scoped PDF rendering, but these can be worked around with snapshot or separate stateless calls.
Maintenance
ActivityMaintained
ResponsivenessMostly unanswered