Skip to main content
Please read the Material Usage Rules on this site.

ZennoPoster MCP: Setup Guide for AI Assistants

Prerequisites: ProjectMaker must be running before connecting any AI assistant. The MCP servers start automatically with ProjectMaker and listen on:

  • BrowserMCP (Browser control) → http://localhost:6108
  • ProjectMCP (Project control) → http://localhost:6107

1. GitHub Copilot​

Steps​

  1. Make sure ProjectMaker is running.
  2. Open your user profile folder: press Win + R, type %USERPROFILE%, press Enter.
  3. Create a file named .mcp.json in that folder (e.g. C:\Users\YourName\.mcp.json).
  4. Paste the following content:
{
  "servers": {
    "BrowserMCP": {
      "type": "http",
      "url": "http://localhost:6108"
    },
    "ProjectMCP": {
      "type": "http",
      "url": "http://localhost:6107"
    }
  }
}
  1. Restart Visual Studio (or reload the Copilot extension).
  2. Copilot will now have access to both MCP servers in all your workspaces.

2. Claude Code (CLI)​

Steps​

  1. Make sure ProjectMaker is running.
  2. Open a terminal.
  3. Run the following two commands:
claude mcp add BrowserMCP --transport http http://localhost:6108
claude mcp add ProjectMCP --transport http http://localhost:6107
  1. Verify the servers are registered:
claude mcp list
  1. The MCP servers are now available globally in all Claude Code sessions.

To remove them later: claude mcp remove BrowserMCP and claude mcp remove ProjectMCP

3. OpenAI Codex CLI​

Steps​

  1. Make sure ProjectMaker is running.
  2. Open a terminal.
  3. Run the following two commands:
codex mcp add BrowserMCP --url http://localhost:6108
codex mcp add ProjectMCP --url http://localhost:6107
  1. Verify:
codex mcp list

Troubleshooting​

The claude or codex command is not recognized​

If the terminal shows an error like:

'claude' is not recognized as an internal or external command,
operable program or batch file.

or (in PowerShell):

claude : The term 'claude' is not recognized as the name of a cmdlet,
function, script file, or operable program.

(same applies to codex), it means the folder containing the CLI executable is not in the PATH environment variable, or the CLI is not installed, or the terminal was not restarted after installing.

Important: the Claude Code website installer (native installer, irm https://claude.ai/install.ps1 | iex) does not add itself to PATH automatically. So "installed from the website but the command is not recognized" is the most common case. Step 2 below fixes it.

Step 1. Find where the CLI is installed​

The location of the executable depends on the install method.

Claude Code:

Install methodFolder containing claude
Website (native): irm https://claude.ai/install.ps1 | iex%USERPROFILE%\.local\bin (e.g. C:\Users\YourName\.local\bin)
npm: npm install -g @anthropic-ai/claude-codethe npm folder, usually %APPDATA%\npm

OpenAI Codex CLI:

Install methodFolder containing codex
Website: irm https://chatgpt.com/codex/install.ps1 | iexthe folder reported by the installer
npm: npm install -g @openai/codexthe npm folder, usually %APPDATA%\npm
Binary from GitHub Releasesthe folder where you extracted codex.exe

You can find the exact npm folder with:

npm config get prefix

Check whether the system sees the command at all (empty output means it is not in PATH):

where.exe claude
where.exe codex

Check that the file exists (for the Claude website install):

Test-Path "$env:USERPROFILE\.local\bin\claude.exe"

If the file is not in any of these folders, the CLI is not installed. Install it using one of the methods from the tables above (npm requires Node.js).

Step 2. Add the folder to the PATH variable​

Use the path you found in Step 1 (e.g. %USERPROFILE%\.local\bin for the Claude website install, or %APPDATA%\npm for an npm install).

Option A: via the Windows GUI

  1. Press Win + R, type sysdm.cpl, press Enter.
  2. Advanced tab -> Environment Variables button.
  3. Under User variables, select Path -> Edit.
  4. Click New and paste the folder, for example: C:\Users\YourName\.local\bin
  5. Click OK in all windows.

Option B: via PowerShell (adds to the user PATH permanently)

# example for the Claude Code website install:
$p = [Environment]::GetEnvironmentVariable('PATH', 'User')
[Environment]::SetEnvironmentVariable('PATH', "$p;$env:USERPROFILE\.local\bin", 'User')

Replace the path with the one relevant to your case. Do not run the command several times in a row, or you will duplicate entries in PATH.

Step 3. Restart the terminal and verify​

PATH changes only take effect in newly opened terminal windows. Close and reopen PowerShell / CMD (or Visual Studio), then check:

claude --version
codex --version

For Claude Code you can also run the built-in diagnostics (checks PATH, conflicting installs, etc.):

claude doctor

If the versions are shown, the commands are recognized correctly and you can go back to the MCP setup steps above.

Common causes if it still does not work​

  • Terminal not restarted. PATH changes only apply in newly opened windows.
  • Multiple installs at once (npm + native) conflict. Keep one and remove the rest.
  • Only the VS Code extension is installed. It does not add the claude command to the terminal. Install the standalone CLI from the website or via npm.

Example Prompts​

Browser Automation​

Start the browser, open a new tab called "search", navigate it to https://google.com,
find the search input, type "ZennoPoster" into it, and click the search button.
Get all open tabs and show me their names and IDs.
In tab 1, get the DOM content filtered by 'input;button;form' and find the login form.
Then fill in the username field with "admin" and the password field with "12345" and submit.
Navigate tab 2 to https://example.com, read the full page DOM text, and summarize what's on the page.

Project Management​

Show me the structure of the current project: list all actions with their IDs and types.
Add a new variable called "LoginUrl" with default value "https://example.com/login".
Get all variables in the project and show me which ones have empty default values.
Create a new list called "Proxies" and add these items to it:
192.168.1.1:8080, 192.168.1.2:8080, 192.168.1.3:8080
Create a table called "Accounts" with 3 columns, then add a row with values:
"user@mail.com", "password123", "active"
Get the current execution logs (all levels) and tell me if there are any errors.
What was the last error in the project? Show me the action ID where it happened.

Combined Browser + Project​

Open a browser, navigate to the login page stored in the project variable "LoginUrl",
fill in the credentials from the "Accounts" table (first row), submit the form,
and save the result page URL back to the variable "LastVisitedUrl".
Get the project structure, find all "NavigateToUrl" actions, and list their URLs.