Good Eggs
Automate Good Eggs grocery browsing and cart actions from your agent via Playwright-backed MCP tools.
Overview
com.pulsemcp/good-eggs is a MCP server for the Build phase that automates Good Eggs grocery shopping with Playwright browser tools.
What is this MCP server?
- Good Eggs account automation through Playwright-driven browser tools
- Required env vars GOOD_EGGS_USERNAME and GOOD_EGGS_PASSWORD
- HEADLESS defaults to true; set false for visible browser debugging
- TIMEOUT defaults to 30000 ms for browser operations
- Stdio MCP via npx good-eggs-mcp-server (v0.1.9)
- Version 0.1.9
- Default HEADLESS true
- Default TIMEOUT 30000 ms
Community signal: 70 GitHub stars.
What problem does it solve?
Agents cannot order or browse grocer sites that lack public APIs, forcing manual shopping outside the workflow.
Who is it for?
Builders prototyping browser-agent demos or personal meal-prep automation on Good Eggs.
Skip if: Production grocery integrations, multi-tenant commerce, or teams without accepting account-password browser auth.
What do I get? / Deliverables
After setup, your agent can run headless or headed Playwright sessions against Good Eggs using MCP tools.
- Good Eggs MCP server registered in agent
- Configurable headless Playwright tool surface for the grocer site
Recommended MCP Servers
Journey fit
Browser automation MCP servers are built-phase integrations that extend what your agent can do on the live web. Playwright session control against a third-party site fits the integrations subphase for external service hooks.
How it compares
Playwright MCP site adapter, not a curated shopping API or ecommerce backend skill.
Common Questions / FAQ
Who is com.pulsemcp/good-eggs for?
Developers and solo builders testing agent-driven browser automation on Good Eggs.
When should I use com.pulsemcp/good-eggs?
When you need MCP tools to log into Good Eggs and automate flows Playwright can reach on the live site.
How do I add com.pulsemcp/good-eggs to my agent?
Configure stdio npx good-eggs-mcp-server, set username and password env vars, optionally HEADLESS and TIMEOUT, then reload MCP.