Sorify MCP
Sorify - 面向AI代理的AI智能QA平台。端到端AI测试 - 完整的用户管理、测试运行器、CI Webhook、调度器、通知、用于测试运行的MCP、创建与管理。附带Chrome扩展和MCP，用于记录事件供AI编写测试。
文档
Next generation AI First - Browser Testing
& browser automation platform
Low Tokens consumption
Built for AI Agents - Claude/Codex
Built for developers
Manage entire workspace through MCP
Create powerful browser automations
With scheduler
Bi-directional webhooks integrations
And a bonus Chrome Extension, with MCP
★ Automate: Automate browser testing, using claude, codex - with skills, mcp, test runners & dashboard.
★ Chrome Extension: Capture browser actions, send to AI to write tests, upload, self heal.
★ Webhooks: 3 types of bi-directional integrations. Trigger runs remotely, or trigger Github Actions or HTTP webhook pre/post a run from Sorify.
★ Ephemeral: Self host, scalable on ephemeral mode.
★ Schedule: In built scheduler to run automated browser tasks.
✴︎ Test Management: Organize test suites and test cases, run them on demand or on a schedule.
✴︎ Test Runners: Playwright-powered execution with full run history.
✴︎ Notifications: Get notified when suites finish or fail.
✴︎ Cookie Manager: Sorify supports per-suite cookie injection from UI, MCP and chrome extension.
✴︎ User Management: Roles, permissions, and per-user IAM.
✴︎ MCP Server: Low token consumption over MCP layer, control all aspects of tests cases, code.
✴︎ Agent Plugins: Claude/Codex plugins included - zero-code test code management.
✴︎ My AI Agent: In-dashboard AI agent your own OpenAI-compatible. Page aware chats that can call every Sorify MCP tool, resumable handoffs to local agents.
✴︎ i18n & 2 modes: Supports Japanese, Chinese, Malay, with dark mode.
Features
WITH ALL MCP CONTROLS - SUPPORTED
▼ Core Testing
・ AI test generation ・ Playwright execution
・ Browser automation ・ Cross-browser support
・ Headless mode ・ Scheduled runs
・ Cron scheduling ・ Run history
・ Run cancellation ・ Status polling
・ Test logs ・ Pass-rate analytics
▼ Test Management
・ Suite management ・ Test case management
・ Bulk test creation ・ Bulk test deletion
・ Suite duplication ・ Test duplication
・ Code version history ・ Version restore
・ Test enable/disable ・ Search and filters
・ Suite bookmarks ・ Dashboard analytics
▼ Sessions and Data
・ Cookie injection ・ Pre-authenticated sessions
・ Storage state upload ・ Suite variables
・ Proxy routing ・ Per-domain proxies
・ Timeout configuration ・ History retention
▼ Access Control
・ User management ・ Role-based permissions
・ Per-suite members ・ Suite sharing
▼ Notifications
・ Teams notifications ・ Email notifications
・ Inline screenshot emails ・ Notification cooldown
・ Digest summaries
▼ Integrations
・ CI webhook trigger ・ Bi-directional webhooks
・ Webhook concurrency guard ・ Webhook token regeneration
・ GitHub Actions dispatch ・ HTTP request hooks
・ Pre-run hooks ・ Post-run hooks
・ GitHub App login
▼ AI and Agents
・ MCP server ・ Low-token consumption
・ Claude plugins ・ Codex plugins
・ My AI Agent web chat ・ Agent chat handoff to MCP
・ AI healing ・ Failure investigation
・ Gateway live lookups
▼ Recorder
・ Chrome extension ・ Session recording
・ Recorded test generation
▼ Deployment
・ Self hosting ・ Ephemeral mode
・ Docker deployment ・ Admin panel
Feature Matrix
▼ Feature Matrix
MCP Dashboard Webhook API
--------------------------------------
・ Suites: list/get/create/update/delete/duplicate ○ ○ — ○
・ Suite schedule: update/delete ○ ○ — ○
・ Suite cookies: upload ○ ○ — ○
・ Suite integrations: GitHub Action/HTTP request (pre/post run hooks) ○ ○ — ○
・ Suite bookmarks: list/toggle ○ ○ — ○
・ Suite members: list/add/update/remove ○ ○ — ○
・ Tests: list/get/create/update/update code/delete/duplicate ○ ○ — ○
・ Tests: bulk-create/bulk-delete ○ ○ — ○
・ Tests: toggle enabled/disabled ○ ○ — ○
・ Runs: trigger/list/get/cancel/delete ○ ○ — ○
・ Runs: status ○ ○ ○ ○
・ Runs: logs ○ ○ — ○
・ Screenshots: list/get ○ ○ — ○
・ Recorder: chrome extension events ○ — — —
・ Suite webhook token: regenerate — ○ — ○
・ Test code-version: restore — ○ — ○
・ Login/register/logout/password reset — ○ — ○
・ Profile: update name/password — ○ — ○
・ Dashboard analytics (stats, recent runs) — ○ — —
・ Admin: manage users (create, list, role, delete, reset password) — ○ — ○
AI Usage
Claude Code
claude /plugin marketplace add https://github.com/rakutentech/sorify.git
Install sorify from that marketplace in Claude Code, then start a new
session. The existing /sorify:gateway, /sorify:generate, and
/sorify:recording commands remain available.
Codex
codex plugin marketplace add https://github.com/rakutentech/sorify.git
codex plugin add sorify@sorify
Create ~/.sorify with SORIFY_URL, SORIFY_USERNAME, and
SORIFY_PASSWORD, then invoke the $sorify:sorify-setup skill once. It registers the
Sorify MCP server and adds the bundled http_headers_helper to Codex's user
configuration without copying the password into that configuration. Restart
Codex and start a new thread afterward.
Use the Codex skills $sorify:sorify-gateway, $sorify:sorify-generate,
$sorify:sorify-recording, and $sorify:sorify-update, or describe the task
naturally. The Codex-only $sorify:sorify-setup skill is not loaded by Claude
Code. For a local checkout, the
setup script can also be run directly:
plugins/sorify/scripts/setup-codex.sh
Verify the connection with:
codex mcp get sorify
The output should show a non-empty http_headers_helper.
SKILL 1 - Sorify MCP
╰─$ cat ~/.sorify
SORIFY_URL=http://localhost:8000/sorify
SORIFY_USERNAME=admin@sorify.local
SORIFY_PASSWORD=changeme
/sorify:gateway Create a test suite called "Awesome App"
/sorify:gateway List latest failing tests
/sorify:gateway Create new test suite. Get requirements from JIRA/GHE/Excel. Write using /sorify:generate
/sorify:gateway Update the test suite http://localhost:8000/sorify/suites/{id} by adding retry twice
AI Healing
/sorify:gateway why my test is failing <name of test>
/sorify:gateway why my test is failing <or-link-to-test>
SKILL 2 - In-Built QA Skills
# Tests from source code (git)
/sorify:generate Scan my code and generate tests for <github.com/your/repo>
# Tests from source code (path)
/sorify:generate Scan my code and generate tests for </path/to/your/source>
# Tests from url (remote)
/sorify:generate Crawl site and generate tests for https://rakuten.co.jp
# Tests from url (local)
/sorify:generate Crawl site and generate tests for http://localhost:3000/my-awesome-app
# Tests from requirements
/sorify:generate Read requirements here <link to docs> <path to docs> <raw paste>
<you got the idea...>
OR SKILL BYO - Bring your own QA Skills
/my:qa:skill Create detailed tests <...>
...then /sorify:gateway once done - upload, run and invetigate failed tests
Chrome Recorder - Record, Capture, Generate, upload (Chrome extension)
This is a chrome extension that works in hybrid mode optionally. While browsing it records browser events, and stores into a file. The sequence of events then can be picked up by AI to better write the test code, works well when more context about the project, such as source code is complemented.
Generate tests from a real recorded session instead of DOM exploration — chrome-mcp-playwright sorify-recorder-mcp
♢ 1. Install the mcp
curl -fsSL https://raw.githubusercontent.com/rakutentech/sorify/master/mcp/install-mcp.sh | sh
♢ 2. Load the Chrome extension
chrome://extensions/ → enable "Developer mode" → "Load unpacked" → select extension/ folder
we don't have npx, sorry
♢ 3. Start the recorder
Sorify recorder should start automatically when you launch Claude Code or
Codex. In Claude Code, check /mcp for
plugin:sorify:sorify-recorder. In Codex, start a new thread after installing
the plugin and invoke $sorify:sorify-recording; it reports if the recorder MCP
server or binary is unavailable.
If not, then start the listener at:
~/.sorify-bin/sorify-recorder-mcp
No 4. Click the extension icon → Connect → Start recording
Perform the clicks/inputs you want turned into a test, then Stop recording.
Tip: to check the port lsof -nP -iTCP:7420 -sTCP:LISTEN
No 5. Generate tests
/sorify:recording latest
In Codex, use $sorify:sorify-recording and ask for the latest recording instead.
Quick Start
Development (local)
# Update: APP_KEY, DB_PASSWORD, MYSQL_ROOT_PASSWORD
cp .env.example .env
composer setup
php artisan dev
# or the whole stack via docker
docker-compose up -d
Verify
http://localhost:8000/sorify
- User: admin@sorify.local
- Password: changeme
See INSTALL.md for other details, self hosting, ephemeral mode, docker.
Integrations
- Sorify Webhook: Trigger Sorify run/runs from outside
- HTTP Webhook: Trigger HTTP from sorify - pre/post run
- Github Action Webhook: Trigger Github action from sorify - pre/post run. Details below:
GitHub, GHES, GHEC integrations
Integration 1: Github Actions → Sorify
Trigger Sorify runs from a workflow using the suite's CI webhook (token auth, no session). Grab the webhook URL from the suite's settings page, store the token as a secret, then:
on: [push]
jobs:
e2e:
runs-on: ubuntu-latest
steps:
- name: Trigger Sorify run
run: |
curl -sf -X POST "$SORIFY_WEBHOOK_URL/trigger" \
-H "Content-Type: application/json" \
-d '{"test_ids": [12, 34]}' # omit to run all active tests
env:
SORIFY_WEBHOOK_URL: ${{ secrets.SORIFY_WEBHOOK_URL }}
- name: Poll run status
run: |
curl -sf "$SORIFY_WEBHOOK_URL/runs/{run}/status"
env:
SORIFY_WEBHOOK_URL: ${{ secrets.SORIFY_WEBHOOK_URL }}
Integration 2: Sorify → Github Actions (pre or post)
GitHub Apps are managed under Admin → GitHub Apps (dashboard). Used for either login or triggering actions from Sorify.
To register an app, follow the walkthrough on the dashboard itself: Admin → GitHub Apps → "How to register".
A workflow dispatched by Sorify looks like this:
on:
workflow_dispatch:
inputs:
# Injected by Sorify — do not edit
sorify_run_id:
type: string
sorify_suite_id:
type: string
# and so on. Custom add from - sorify's suite/{id} > settings
jobs:
sorify:
name: Sorify
steps:
- name: Show Sorify context
run: |
echo "sorify_run_id=${{ github.event.inputs.sorify_run_id }}"
HTTP API Reference
See API.md for the complete endpoint list and sample curl requests.
Owners
 MarikoKikugawa |
 asghar-ahmed |
 HiromichiHagiwara | |
 kevincobain2000 |
 pulkit-kathuria |
 chetra-tep |
 chetratep |
Contribution
- Raise an issue or PR to
master
License
Licensed under the Apache License, Version 2.0.
The Chrome extension in extension/ is licensed separately
under the BSD 3-Clause License, which prohibits
publishing it (or a derivative) under the "Sorify Recorder" name without
permission. See extension/README.md for details.
CHANGE LOG
- v1 - Intial Release
- v1.1 - Batteries added on user management, mcp enhancement
- v1.2 - Chrome Extension to record and write playwright tests
- v1.3 - Skills updated, MS Teams notifications links to a screenshot, dashboard has admin editable msg
- v1.4 - Manage users from MCP.
- v1.5 - i18n support for English and Japanese for now.
- v1.6 - i18n support for Malay, Simplified Chinese. Extension captures file uploads, iframes, tabs, network. oAuth login, with Avatar. Duplicate a test suite (background copy of tests) and duplicate a test case, available on the dashboard and via MCP (
duplicate_suite,duplicate_test). - v1.7 - Cookies support, variables support.
- v1.8 - MCP supports runs. Auto redirect after login page. Support for one time CI webhook and who ran the CI.
- v1.9 - Chrome extension memory leak fix. Support pre/post webhooks for multiple connectors.
- v2.0 - Ephemeral mode
- v2.1 - My AI Agent: in-dashboard agent chat (OpenAI-compatible profiles, page context, MCP handoff) and AI model attribution on test code.