Log inSubmit server
Codify MCP logo

Codify MCP

Create reusable Playwright browser automation tools executed by Apify Agent through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Codify MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "codify-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "codify-mcp"
      ],
      "env": {
        "APIFY_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y codify-mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1d ago.

Overview

The codify-mcp MCP server lets AI assistants run custom browser automation through Apify Agent. It accepts one or more tool definitions as JSON command-line arguments and exposes them through MCP. Each definition can include an input schema, Playwright script, and optional Apify actor ID. Reach for it when you need reusable scraping or browser workflows without maintaining separate tool files.

Use cases

  • Create a reusable product-page scraper
  • Expose browser actions as assistant-callable tools
  • Run parameterized Playwright workflows through Apify
  • Group related automation tools into separate MCP processes

Key features

  • JSON-defined MCP tools
  • Playwright browser scripts
  • Apify actor selection
  • Command-line multi-tool loading
  • Schema-based tool inputs
  • Environment or CLI authentication

Tools2

What Codify MCP lets your agent do. Expand a tool for its parameters.

Self-reported~49 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

12/12 checks healthy over the last 57d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 16d ago via OSV.dev · codify-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads146Package downloads in the last 30 days.
Last commit9mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed2Callable tools this server registers over MCP.

How Codify MCP works

What codify-mcp MCP server does

The codify-mcp MCP server turns user-defined browser workflows into MCP tools that an AI assistant can call. Each tool has a name, description, input schema, and implementation. The implementation runs JavaScript Playwright code through an Apify actor, allowing the workflow to navigate pages, inspect content, and return a value or object.

Tool definitions are supplied as JSON strings on the command line. You can start one tool for development or pass several definitions to expose a larger collection. The project is intended for reusable browser tasks such as extracting information from a page, provided the required automation logic is written in the tool definition.

How it works

When the process starts, it reads the JSON arguments, registers valid definitions with the MCP server, and makes them available to the connected assistant. During execution, the script receives an inputs object containing the caller's parameters and a page object for Playwright browser automation.

The default actor is cyberfly/apify-agent. A definition can set another actorId when a different Apify actor should execute the script. The script must be valid JavaScript and should await browser operations before returning its result.

The codify-mcp MCP server is stateless: each invocation is independent. Tool definitions remain in the command arguments rather than separate configuration files. Once installed, the bundled dependencies can run locally without downloading additional dependencies.

Setup and configuration

Run the package directly with npx codify-mcp or install it globally with npm. Append each tool definition as a JSON argument. Multiple arguments create multiple exposed tools.

Apify authentication is required for tool execution. The server first checks APIFY_TOKEN, then checks ~/.apify/auth.json, which can be created with apify login. If neither source provides a token, execution fails. The token can also be placed in an MCP client's environment configuration.

Claude Desktop configuration uses an MCP server entry with command: "npx", the package name in args, and optionally APIFY_TOKEN in env. The README also names Cursor and VS Code as connection targets.

Tools and capabilities

  • Define MCP tools with names, descriptions, and JSON input schemas.
  • Run Playwright scripts with access to inputs and page.
  • Select an Apify actor with actorId, or use cyberfly/apify-agent by default.
  • Pass one or many tool definitions through command-line arguments.
  • Support schema fields such as required values, defaults, integer types, and enumerations.
  • Return script-generated values or objects to the calling assistant.

Limitations and notes

The codify-mcp MCP server does not generate the automation script itself. The supplied JavaScript must be valid, use the provided objects correctly, and return a result. Missing or malformed JSON arguments produce tool-registration errors, while missing Apify authentication prevents execution.

For collections of 50 or more tools, the README recommends splitting them across multiple MCP server processes. Authentication sessions through the project's separate Login component are described as a future item, so this listing does not establish that feature as available.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Codify MCP

codify-mcp is an MCP server that connects AI assistants to Apify Agent for custom browser automation. Its main tools are user-defined MCP tools with Playwright `script` code and an optional `actorId`. Scripts receive `inputs` and a Playwright `page` object, then return results from the automated browser task.

Install it with `npm install -g codify-mcp`, or run it directly with `npx codify-mcp`. Pass each tool definition as a JSON command-line argument.

Set `APIFY_TOKEN` or run `apify login` to save credentials in `~/.apify/auth.json`. The server checks the environment variable first and then the auth file. Without a token from either source, tool execution fails.

Yes, Cursor is named as a supported connection target in the README. Configure the MCP server using the `npx` command, the `codify-mcp` package name, and JSON tool definitions as arguments, with `APIFY_TOKEN` supplied when needed.

Related MCP servers

All in Browser Automation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewCodify MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/codify-mcp?style=directory)](https://allmcps.com/mcp/codify-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/codify-mcp"><img src="https://allmcps.com/api/badge/codify-mcp?style=directory" alt="Codify MCP on AllMCPs" /></a>