Steel MCP Server

🚀 Steel MCP Server

Steel MCP Server is a powerful tool that can be used in conjunction with Claude Desktop, providing users with efficient and stable services.

🚀 Quick Start

📦 Installation

Install via Smithery

To automatically install the Steel MCP Server for Claude Desktop via Smithery, use the following command:

npx -y @smithery/cli install @steel-dev/steel-mcp-server --client claude

Local Development

1. Clone the repository.
2. Install dependencies:

npm install

3. Build the project:

npm run build

4. Start the server:

npm start

💻 Usage Examples

We asked Claude to showcase its new features and decided to explore the latest developments (such as "Sora"). Then, we created an interactive visualization to demonstrate the data behind the model and how it works.

Please note that due to GitHub's limit of video size to no more than 10MB, the video quality may not be high. We apologize for any inconvenience.

📚 Documentation

Configuration Example

To use Steel Voyager in Claude Desktop, 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 the environment variables as needed:

• If running locally or in a self-hosted environment, keep "STEEL_LOCAL": "true" and optionally add "STEEL_BASE_URL": "http://localhost:3000".
• If running in cloud mode, change "STEEL_LOCAL": "true" to "STEEL_LOCAL": "false" and provide a valid "STEEL_API_KEY".

Troubleshooting Common Issues

1. Verify the Steel API Key

When using the cloud service, ensure that you provide a valid Steel API key and confirm that the local Steel instance is running. Also, check your network connection.

2. Add a Delay

If you encounter issues with page marking or screenshot transfer, you can add a delay via the GLOBAL_WAIT_SECONDS environment variable in the configuration:

export GLOBAL_WAIT_SECONDS=10 # Set to the desired number of seconds

3. Ensure the Page is Fully Loaded

Check if the page is fully loaded and confirm that the viewport size is set correctly. Make sure your system has enough memory to capture screenshots.

4. Manually Clean Up Sessions

Currently, the session cleanup function is not perfect. It is recommended to manually release session resources after completing tasks.

5. Prompting Techniques

Prompt Claude in an appropriate way to better guide its output. Avoid using overly broad or vague instructions.

🤝 Contribution Guidelines

If you wish to contribute to the project, please refer to the following guidelines:

• Submit a Pull Request (PR): Ensure that your submission includes a clear description of the changes, the motivation behind them, and relevant documentation updates.
• Report Issues: Report any issues or feature requests on the Issues page.
• Code Style: Follow the existing code style and naming conventions in the project to ensure code quality and maintainability.

📄 License

Please refer to the project's LICENSE file for detailed licensing information.