Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"steel-puppeteer": {
"env": {
"STEEL_LOCAL": "false",
"STEEL_API_KEY": "your_api_key_here"
},
"args": [
"path/to/steel-puppeteer/dist/index.js"
],
"command": "node"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@steel-dev/steel-mcp-server' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @steel-dev/steel-mcp-server against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in browser
Browser automation with Puppeteer for web scraping and testing
🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
MCP server for Firecrawl — search, scrape, and interact with the web. Supports both cloud and self-hosted instances. Features include web search, scraping, page interaction, batch processing, and LLM-powered content analysis.
The Apify MCP server enables your AI agents to extract data from social media, search engines, maps, e-commerce sites, or any other website using thousands of ready-made scrapers, crawlers, and automation tools available on the Apify Store.
MCP Security Weekly
Get CVE alerts and security updates for Steel Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
https://github.com/user-attachments/assets/25848033-40ea-4fa4-96f9-83b6153a0212
A Model Context Protocol (MCP) server that enables LLMs like Claude to navigate the web through Puppeteer-based tools and Steel. Based on the Web Voyager framework, it provides tools for all the standard web actions click clicking/scrolling/typing/etc and taking screenshots.
Ask Claude to help you with tasks like:
Below is a streamlined guide to run Steel Voyager inside Claude Desktop. You only need to adjust the environment options to switch between Steel Cloud and a local/self-hosted instance.
Clone and build the project:
git clone https://github.com/steel-dev/steel-mcp-server.git
cd steel-mcp-server
npm install
npm run build
Configure Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json) by adding a server entry:
{
"mcpServers": {
"steel-puppeteer": {
"command": "node",
"args": ["path/to/steel-voyager/dist/index.js"],
"env": {
"STEEL_LOCAL": "false",
"STEEL_API_KEY": "YOUR_STEEL_API_KEY_HERE",
"GLOBAL_WAIT_SECONDS": "1"
}
}
}
}
Start Claude Desktop. It will automatically launch this MCP server in Cloud mode.
(Optional) You can view or manage active Steel Browser sessions in your dashboard.
Ensure your local or self-hosted Steel service is running (e.g., using the open-source Steel Docker image).
Clone and build the project (same as above if not done yet):
git clone https://github.com/steel-dev/steel-mcp-server.git
cd steel-mcp-server
npm install
npm run build
Configure Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json) for local mode:
{
"mcpServers": {
"steel-puppeteer": {
"command": "node",
"args": ["path/to/steel-voyager/dist/index.js"],
"env": {
"STEEL_LOCAL": "true",
"STEEL_BASE_URL": "http://localhost:3000",
"GLOBAL_WAIT_SECONDS": "1"
}
}
}
}
Start Claude Desktop, which will connect to your locally running Steel and launch Steel Voyager in local mode.
(Optional) To view sessions locally, you can visit your self-hosted dashboard (localhost:5173) or logs specific to your Steel runtime environment.
That’s it! Once Claude Desktop starts, it will orchestrate the MCP server behind the scenes and let you interact with the web automation capabilities through Steel Voyager.
For more info on getting set up or if you're having issues, check out the MCP set-up docs: http