--- title: "Set up GeoRanker MCP Beta" description: "Install a local stdio SEO or Web Scraping MCP client for your AI assistant using the reviewed runtime, enrollment and host configuration requirements." canonical: "https://www.georanker.com/mcp/setup" last_modified: "2026-09-18" --- # Set up GeoRanker MCP Beta > Install a local stdio SEO or Web Scraping MCP client for your AI assistant using the reviewed runtime, enrollment and host configuration requirements. Choose SEO MCP for localized search and SEO reports, or Web Scraping MCP for supported public-page retrieval. Install one or both as separate host entries. ### Install SEO MCP Reviewed public client: 0.13.1 (2026-09-18). Website release status: Beta. Requires Node.js 22.22.2+ on the 22 release line, 24.15.0+ on the 24 release line, or 26.0.0+; npm and Git. Install from GitHub source. The reviewed npm packages are unpublished; there is no supported npx installation for this release. ```sh git clone https://github.com/georanker/georanker-seo-mcp.git cd georanker-seo-mcp npm ci npm run build node dist/src/cli.js --setup ``` The setup check enrolls the installation, saves its local credential and verifies tool contracts. It does not submit a data query. For Codex, run from the installed client directory: ```sh codex mcp add georanker-seo -- node "$PWD/dist/src/cli.js" ``` #### OpenClaw Use a current OpenClaw release with native MCP support. Run these commands from the client folder on the machine where your OpenClaw Gateway runs. The second command checks the connection. Start a new turn; if the tools have not appeared, restart your Gateway. ```sh openclaw mcp add georanker-seo --command node --arg "$PWD/dist/src/cli.js" --cwd "$PWD" openclaw mcp doctor georanker-seo --probe ``` [Official host MCP guide](https://docs.openclaw.ai/tools/mcp) #### Hermes Agent Run these commands from the client folder on the machine where Hermes runs. Choose the GeoRanker tools you want when prompted. The second command checks the connection. Start Hermes with hermes chat, or use /reload-mcp in an existing chat. ```sh hermes mcp add georanker-seo --command node --args "$PWD/dist/src/cli.js" hermes mcp test georanker-seo ``` [Official host MCP guide](https://hermes-agent.nousresearch.com/docs/user-guide/features/mcp) [Other assistant configuration guides](https://www.georanker.com/mcp/seo#install). These guides require a host that can launch a local Node.js process. - [Tool catalog and release behavior](https://github.com/georanker/georanker-seo-mcp/blob/432ec1688fd507cb955067bd022876b93047169f/README.md) - [Installation and update controls](https://github.com/georanker/georanker-seo-mcp/blob/432ec1688fd507cb955067bd022876b93047169f/docs/install.md) - [Inputs, outputs and result limits](https://github.com/georanker/georanker-seo-mcp/blob/432ec1688fd507cb955067bd022876b93047169f/docs/examples.md) - [SEO report contracts and admission units](https://github.com/georanker/georanker-seo-mcp/blob/432ec1688fd507cb955067bd022876b93047169f/docs/seo-reports.md) - [Client privacy and data flow](https://github.com/georanker/georanker-seo-mcp/blob/432ec1688fd507cb955067bd022876b93047169f/docs/privacy.md) - [Version and runtime requirements](https://github.com/georanker/georanker-seo-mcp/blob/432ec1688fd507cb955067bd022876b93047169f/package.json) ### Install Web Scraping MCP Reviewed public client: 0.13.1 (2026-09-18). Website release status: Beta. Requires Node.js 22.22.2+ on the 22 release line, 24.15.0+ on the 24 release line, or 26.0.0+; npm and Git. Install from GitHub source. The reviewed npm packages are unpublished; there is no supported npx installation for this release. ```sh git clone https://github.com/georanker/georanker-web-scraping-mcp.git cd georanker-web-scraping-mcp npm ci npm run build node dist/src/cli.js --setup ``` The setup check enrolls the installation, saves its local credential and verifies tool contracts. It does not submit a data query. For Codex, run from the installed client directory: ```sh codex mcp add georanker-web-scraping -- node "$PWD/dist/src/cli.js" ``` #### OpenClaw Use a current OpenClaw release with native MCP support. Run these commands from the client folder on the machine where your OpenClaw Gateway runs. The second command checks the connection. Start a new turn; if the tools have not appeared, restart your Gateway. ```sh openclaw mcp add georanker-web-scraping --command node --arg "$PWD/dist/src/cli.js" --cwd "$PWD" openclaw mcp doctor georanker-web-scraping --probe ``` [Official host MCP guide](https://docs.openclaw.ai/tools/mcp) #### Hermes Agent Run these commands from the client folder on the machine where Hermes runs. Choose the GeoRanker tools you want when prompted. The second command checks the connection. Start Hermes with hermes chat, or use /reload-mcp in an existing chat. ```sh hermes mcp add georanker-web-scraping --command node --args "$PWD/dist/src/cli.js" hermes mcp test georanker-web-scraping ``` [Official host MCP guide](https://hermes-agent.nousresearch.com/docs/user-guide/features/mcp) [Other assistant configuration guides](https://www.georanker.com/mcp/web-scraping#install). These guides require a host that can launch a local Node.js process. - [Tool catalog and release behavior](https://github.com/georanker/georanker-web-scraping-mcp/blob/b1f27cde5c9ccc37f251caa4fc0c0687823449f5/README.md) - [Installation and update controls](https://github.com/georanker/georanker-web-scraping-mcp/blob/b1f27cde5c9ccc37f251caa4fc0c0687823449f5/docs/install.md) - [Inputs, outputs and result limits](https://github.com/georanker/georanker-web-scraping-mcp/blob/b1f27cde5c9ccc37f251caa4fc0c0687823449f5/docs/examples.md) - [Client privacy and data flow](https://github.com/georanker/georanker-web-scraping-mcp/blob/b1f27cde5c9ccc37f251caa4fc0c0687823449f5/docs/privacy.md) - [Version and runtime requirements](https://github.com/georanker/georanker-web-scraping-mcp/blob/b1f27cde5c9ccc37f251caa4fc0c0687823449f5/package.json) ## Installation, enrollment and version questions ### How do AI agents connect to GeoRanker MCP? The documented integration is a local stdio MCP client launched by your assistant. That client connects over HTTPS to GeoRanker's hosted service. Use a host that can launch local Node.js processes and follow its configuration guide. A cloud-only connector needs a separately supported remote authentication flow; entering a hosted endpoint URL alone is not the documented installation path. [Reviewed first-party documentation](https://github.com/georanker/georanker-seo-mcp/blob/432ec1688fd507cb955067bd022876b93047169f/docs/install.md) ### What does no API key to configure mean? The client enrolls automatically and stores an installation credential and signing identity locally. You do not enter a reusable provider API key or create a GeoRanker account for the Beta trial. The two clients share installation state for the same service origin. This enrollment is not OAuth. The setup check verifies enrollment and tool contracts without submitting a data query; subsequent tool calls use the configured allowance. [Reviewed first-party documentation](https://github.com/georanker/georanker-seo-mcp/blob/432ec1688fd507cb955067bd022876b93047169f/docs/privacy.md) ### What data leaves my machine and what is stored locally? The client sends requested search arguments or the public URL, an installation identifier, a revocable token and a persisted device signal to GeoRanker over HTTPS. GeoRanker uses its upstream infrastructure to process the request. Local identity and credentials normally live under ~/.config/georanker-search-mcp/client/; GEORANKER_STATE_DIR can change that location. Keep this state private. Shared result caching follows service isolation rules, so avoid secret URLs or sensitive content. Removing the host configuration does not revoke the installation or erase its saved credentials. [Reviewed first-party documentation](https://github.com/georanker/georanker-seo-mcp/blob/432ec1688fd507cb955067bd022876b93047169f/docs/privacy.md) ### How are MCP client versions and updates managed? The public clients reviewed on 2026-09-18 are version 0.13.1; the website presents both products as Beta. The launcher checks for verified GitHub release packages at startup and every five minutes. It verifies release provenance and installs locked production dependencies without lifecycle scripts. Compatible worker updates apply during an idle period; calls are not replayed. Set GEORANKER_MCP_AUTO_UPDATE=0 in the host environment to review and manage releases yourself. Update downloads contact GitHub, npm and signature-verification services; the client privacy guide explains this data flow. [Reviewed first-party documentation](https://github.com/georanker/georanker-seo-mcp/blob/432ec1688fd507cb955067bd022876b93047169f/docs/install.md) ### Can I install GeoRanker MCP with npx? The reviewed release uses a GitHub source installation: clone, install dependencies, build, run the setup check and configure your host. Its npm packages are unpublished, so an npx command is not available for this release. Requirements are Node.js 22.22.2+ on the 22 release line, 24.15.0+ on the 24 release line, or 26.0.0+; npm and Git. Public source availability does not imply an open-source license; the packages are marked UNLICENSED. Repository metadata is not an official MCP Registry submission. [Reviewed first-party documentation](https://github.com/georanker/georanker-seo-mcp/blob/432ec1688fd507cb955067bd022876b93047169f/README.md) [Request more free Beta credits](https://www.georanker.com/mcp/credits)