reviewwebsite

This MCP server provides a bridge between AI assistants and the ReviewWebsite.com API to manage website reviews and related data. It exposes tools for creating, reading, updating, and deleting reviews, converting URLs to Markdown, extracting structured data from pages, scraping content, extracting links, summarizing websites, and generating SEO insights such as keyword ideas and traffic analysis. Interactions are performed via the MCP protocol over the stdio transport by default, or via HTTP if you configure the HTTP transport. Use the included CLI commands to exercise the available capabilities, or integrate the MCP server into your own AI workflows to automate review-related tasks and data extraction.

Prerequisites:

• Node.js (>= 18.x) installed on your machine
• Git installed for cloning the repository

Step 1: Clone the repository

git clone https://github.com/mrgoonie/reviewwebsite-mcp-server.git
cd reviewwebsite-mcp-server

Step 2: Install dependencies

npm install

Step 3: Build (if applicable) and start the server

• Development (stdio transport by default):

npm run dev:server

• If you want HTTP transport in front, ensure the server is built and start with:

npm run dev:server:http

Step 4: Verify the server is running

• For stdio transport, connect via MCP client as described in the README.
• For HTTP transport, the server is typically available at http://127.0.0.1:8080/mcp by default (as documented in the README).

Notes and tips:

• The MCP server supports multiple transports; by default, stdio is used for CLI interactions, while HTTP transport can be enabled via configuration described in the README.
• Environment variables for HTTP transport include MCP_HTTP_HOST, MCP_HTTP_PORT, and MCP_HTTP_PATH. Set these to customize where the HTTP MCP endpoint is exposed.
• When using the CLI tools, you must provide an API key for ReviewWebsite.com where required (e.g., get-ai-models, create-review, convert-to-markdown, etc.).
• The npm package name for this server is reviewwebsite-mcp-server. Make sure to reference the correct path to the built server (dist/index.js) if you’re running a built version.
• If you encounter transport or authentication issues, verify that the host/port bindings match your client configuration and that API keys have the necessary permissions for the requested actions.