Get Started
Reference

Troubleshooting

If you get an error, it is generally because of one of the following:

  1. The MCP server is not running.
  2. The browser is not connected to the MCP server.

MCP server is not running

If the MCP server is not running, you will get errors when trying to run commands that use the MCP server.

In order to run commands, the Blueprint MCP server must be running. View the list of MCP servers in your application to ensure that the Blueprint MCP server is running.

Client closed

If you see the message Client closed and clicking reload doesn't fix it, try removing @latest from the MCP server config so that you are using the package as @railsblueprint/chrome-mcp instead of @railsblueprint/chrome-mcp@latest.

Browser is not connected to the MCP server

In order to connect the browser to the MCP server, install the Blueprint MCP extension and click the "Connect" button.

Other errors

If you encounter other errors, please file an issue on GitHub.

Start automating