TypeScript Model Context Protocol (MCP) server for ReviewWebsite. Includes CLI support and extensible structure for connecting AI systems (LLMs) to
TypeScript Model Context Protocol (MCP) server for ReviewWebsite. Includes CLI support and extensible structure for connecting AI systems (LLMs) to ReviewWeb.site API. Exposed over MCP by the reviewwebsite.com mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
This project provides a Model Context Protocol (MCP) server that connects AI assistants to ReviewWebsite.com API to create and manage website reviews, extract data, convert URLs to markdown, and more.
Model Context Protocol (MCP) is an open standard that allows AI systems to securely and contextually connect with external tools and data sources.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Everything the assistant can do here goes through one of these:
Purpose — Define MCP tools with schemas and descriptions for AI assistantsNaming — Files should be named .tool.ts with types in .types.tsPattern — Each tool should use zod for argument validationYou will need 4 environment variables: DEBUG, REVIEWWEBSITE_API_KEY, MCP_HTTP_HOST, MCP_HTTP_PATH. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. ReviewWebsite.Com's toolset — Purpose, Naming, Pattern — is a fair guide to whether it matches your workflow. It is maintained by mrgoonie; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Purpose | Define MCP tools with schemas and descriptions for AI assistants |
| Naming | Files should be named <feature>.tool.ts with types in <feature>.types.ts |
| Pattern | Each tool should use zod for argument validation |
**For remote HTTP configuration:**
```json
{
"mcpServers": {
"reviewwebsite": {
"type": "http",
"url": "http://localhost:8080/mcp"
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| DEBUG | Configuration value read at startup. | Optional |
| REVIEWWEBSITE_API_KEY | Credential the server authenticates with. | Yes |
| MCP_HTTP_HOST | Endpoint or connection string the server talks to. | Optional |
| MCP_HTTP_PATH | Filesystem location the server is allowed to use. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.