Steel Dev Steel MCP Server

🚀 Piano MCP Project

The Piano MCP project is a project that provides certain functions and features. It can be configured and run in different modes to meet various needs.

🚀 Quick Start

Local Development

1. Clone the repository.
2. Install dependencies:

npm install

3. Build the project:

npm run build

4. Start the server:

npm start

📦 Installation

Local Mode

1. Set STEEL_LOCAL="true".
2. (Optional) Set STEEL_BASE_URL to point to your custom domain's Steel service. Otherwise, the default is http://localhost:3000.
3. No API Key is required.
4. Puppeteer connection address: ws://0.0.0.0:3000

Cloud Mode

1. Set STEEL_LOCAL="false".
2. Set STEEL_API_KEY so that Steel Voyager can authenticate with the cloud service (or a self-hosted Steel instance).
3. The default STEEL_BASE_URL is https://api.steel.dev. Override the setting if you need to change it.
4. Puppeteer connection address: wss://connect.steel.dev?sessionId=…&apiKey=…

Configure Claude Desktop Version

Add the following content to the configuration file (usually located at ~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "steel-puppeteer": {
      "command": "node",
      "args": ["path/to/steel-puppeteer/dist/index.js"],
      "env": {
        "STEEL_LOCAL": "true",
        "STEEL_API_KEY": "your_api_key_here"
      }
    }
  }
}

Adjust environment variables according to your needs:

• Local or self-hosted: "STEEL_LOCAL": "true", optionally "STEEL_BASE_URL": "http://localhost:3000"
• Cloud: "STEEL_LOCAL": "false", add "STEEL_API_KEY": "<YourKey>"

💻 Usage Examples

Claude demonstrated its new features, studied the latest Sorah model, and created an interactive visualization to demonstrate the data and working principles.

(Video file size should not exceed 10MB due to GitHub limitations)

📚 Documentation

Frequently Asked Questions

1. Ensure that the Steel API Key is correct and the cloud service network connectivity is normal.
2. Add the delay configuration GLOBAL_WAIT_SECONDS to solve page loading problems.
3. Check the page loading status and viewport size settings.
4. Manually release sessions to avoid resource leakage.
5. Provide reasonable prompts to improve performance.

Contribution Guidelines

1. Fork the repository.
2. Create a feature branch.
3. Submit a pull request.

Please include:

• Description of changes
• Motivation
• Documentation updates

⚠️ Important Note

This project is based on the Web Voyager codebase and is still in the experimental stage. Do not use it in a production environment.