ProdPoke

io.github.prodpokePublished by GitHub account prodpokev1.0.0Updated Oct 27, 2026

AI QA tester — real browsers scan sites for bugs, SEO, perf, and accessibility issues via chat.

VerifiedStreamable HTTPWeb executableBrowser AutomationSecurity & Monitoring

Overview

AI-generated overview

Hosted QA tester that runs real Playwright browsers on your site and returns accessibility, SEO, performance and flow bugs through chat.

What you can do
  • Chat with a QA tester to scan a URL, test a user flow, or dig into earlier findings, with state kept across turns via a session ID.
  • Check the remaining scan credits on the account.
When to use it
Useful when you want an assistant to audit a live website for accessibility, SEO, performance, visual regressions or broken flows without installing or managing a browser locally, and when you want findings to accumulate across a multi-step QA conversation.
Requirements
Remote streamable HTTP endpoint; no local install. A ProdPoke account and an API key sent as an Authorization bearer token (pp_ prefix). Clients that only support stdio need the mcp-remote bridge via npx. Scans consume credits; the free tier starts with 500.
Before you install
The API key is a secret shown once and must be kept out of shared configs; it can be revoked and re-minted. Scans run on ProdPoke servers, so the URLs you submit and the pages the browser visits are sent to a third party. Scans spend credits, and deeper flow tests cost far more than a standard scan. Each step times out at 120 seconds.

Installation

In SourceWeft

  1. Open ProdPoke in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.prodpoke%2Fprodpoke-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "prodpoke": {
      "type": "http",
      "url": "https://prodpoke.com/v1/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

ProdPoke MCP Server

A QA tester inside your AI. Chat with ProdPoke from Claude, Cursor, or any MCP client. It launches real Playwright browsers, finds real bugs, and remembers what you talked about across turns.

[License: MIT] [MCP Protocol] [Website]

Hosted, not installed. Just paste a config into your MCP client and go.

Landing page · Get an API key · Pricing · ProdPoke

[ProdPoke MCP demo — scanning a site from Claude Desktop]

What it does

ProdPoke is a remote, stateful MCP server that runs real-browser QA for any website. You describe what you want in plain English; ProdPoke spins up a headless Playwright session, navigates the site, and streams back structured findings — accessibility, SEO, performance, user-flow bugs, visual regressions, broken CTAs, and more.

Unlike local tools, everything runs on ProdPoke infrastructure. No Chromium to install, no browser containers to manage, no cleanup.

Available tools

ToolDescriptionParameters
chatTalk to ProdPoke like a QA tester — scan a URL, test a flow, investigate findings, set session preferences. Stateful via session_id.message (required), session_id (optional)
get_credit_balanceCheck your remaining scan credits.—

Example chat response

json
{  "session_id": "a1b2c3d4-...",  "response": "Found 3 issues on https://example.com...",  "findings": [    {      "severity": "high",      "category": "accessibility",      "title": "Missing alt text on 4 images",      "description": "Images in the hero section lack alt attributes..."    },    {      "severity": "medium",      "category": "seo",      "title": "Missing meta description",      "description": "The page has no meta description tag..."    }  ],  "session_context": {    "url_being_tested": "https://example.com",    "message_count": 2,    "has_findings": true  }}

Setup

1. Get your API key

  1. Sign up for a ProdPoke account — the free tier includes 500 credits, enough for a first scan.
  2. Go to Settings → API Keys.
  3. Click Create new key and copy it immediately (it's shown once; you can't recover it later, but you can revoke and re-mint).

Keys look like pp_ followed by 64 hex characters.

2. Paste the config into your MCP client

Claude Desktop / Cursor / Claude Code (streamable HTTP — recommended)
json
{  "mcpServers": {    "prodpoke": {      "type": "streamable-http",      "url": "https://prodpoke.com/v1/mcp",      "headers": {        "Authorization": "Bearer pp_YOUR_KEY_HERE"      }    }  }}

Config file locations:

  • Claude Desktop (macOS): ~/Library/Application Support/Claude/claude_desktop_config.json
  • Claude Desktop (Windows): %APPDATA%\Claude\claude_desktop_config.json
  • Claude Code: .mcp.json in your project root
  • Cursor: Settings → MCP Servers

Fully restart the client after editing.

Clients that only support stdio (via mcp-remote bridge)
json
{  "mcpServers": {    "prodpoke": {      "command": "npx",      "args": [        "mcp-remote",        "https://prodpoke.com/v1/mcp",        "--header",        "Authorization: Bearer ${PRODPOKE_API_KEY}"      ],      "env": {        "PRODPOKE_API_KEY": "pp_YOUR_KEY_HERE"      }    }  }}

Uses mcp-remote to proxy stdio ↔ streamable HTTP.

3. Start chatting

Try any of these:

Multi-step sessions

The chat tool is stateful. Each response includes a session_id; pass it back to continue the conversation with full context:

  1. chat("Scan https://mysite.com") — starts a session, runs the scan, returns session_id + findings.
  2. chat("Dig deeper into the accessibility issues", session_id="...") — builds on the prior scan.
  3. chat("Now test the checkout flow", session_id="...") — runs a targeted test, knows about the earlier findings.
  4. chat("What should I fix first?", session_id="...") — answers from the accumulated session context.

Sessions persist across MCP client restarts for the lifetime of the key.

How it works

Your MCP client  ──Authorization: Bearer pp_...──▶  https://prodpoke.com/v1/mcp                                                       │                                                       ▼                                           Orchestrator classifies intent                                                       │                                                       ▼                                           Playwright worker on ProdPoke                                            infrastructure runs the scan                                                       │                                                       ▼                                          Findings streamed back as a                                               structured `chat` response

Nothing is installed on your machine. Scans run on our servers. You pay per scan in credits (see below).

Pricing

PlanCreditsPrice
Free tier500 credits$0
Watch10,000 / month$15 / month
Watch Pro50,000 / month$49 / month
Top-up packs1,000 – 50,000From $3

A standard scan costs roughly 10 credits. Deeper workflows — full user-flow tests, competitor comparisons — run 400–500 credits. See full pricing →

The error message when you're out of credits is explicit: "Insufficient credits. You need N but have M.", so your AI client can surface it clearly.

Troubleshooting

  • 401 Missing Authorization header — your client didn't send the Authorization header. Double-check the config (the key goes in headers, not env, for streamable HTTP).
  • 401 Invalid or revoked API key — the key was revoked or typed incorrectly. Re-mint at /app/settings/keys.
  • The tool responds but never runs a scan — ask it to scan a specific URL. ProdPoke needs a URL to launch a browser; it won't guess.
  • Scan hangs for >2 minutes — the MCP call times out at 120 seconds per step. Long flows should be split into multiple chat turns using session_id.

Links

License

MIT — see LICENSE.

Source: README.md at commit 4cf77e7

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts