About AgentKit Browser Automation
AgentKit Browser Automation is a browser agent built with Inngest-AgentKit and Firebase-Genkit for web navigation and task execution. It uses a separate Playwright MCP server for browser access.
Key features
- 01Web navigation
- 02Browser task execution
- 03Built with Inngest-AgentKit and Firebase-Genkit
Use cases
- 01Automating web navigation
- 02Executing tasks in a browser
MCP support
It uses a separately started Playwright MCP server for browser automation.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEgentKit Browser Automation
A browser agent built with Inngest-AgentKit and Firebase-Genkit, featuring an agent system for intelligent web navigation and task execution.
Getting Started
Prerequisites
- Node.js (v20 or higher)
- npm or yarn
- OpenAI API key (for GPT models)
- Goolge AI key (for gemini models)
Installation
- Clone the repository:
git clone https://github.com/tmahesh/playwright-agent.git
cd playwright-agent
- Install dependencies:
npm install
- Set up environment variables:
cp .env.sample .env
# Edit .env with your API keys
- Start plawright mcp server in a seperate terminal window
npx @playwright/mcp@latest --port 8931
- To run with genkit sdk
npx tsx genkit.ts
#dev server(optional but recommended)
#It has fantastic observaibility built-in with opentelemetry
npx genkit start -- npx tsx --watch genkit.ts
- If you want to try agentkit of inngest-cli (NOTE: the names are very close agentkit nad genkit)
npx tsx agentkit.ts
#dev-server (optional)
npx inngest-cli@latest dev --no-discovery -u http://localhost:3000/api/inngest -v
Acknowledgments
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.