MagickMonkey logoMagickMonkey
Sign in

Self-hosted userscript workspace

Script once.Run on yours.

Open-source tooling for a private script library—web editor, Chrome extension shell, Tampermonkey launcher, and AI automation. Deploy your own instance; no shared platform required.

Deploy your instanceSetup guideOpen editor

Already deployed this repo? Use Open editor to sign in to your instance.

Self-hosted on your infra
Editor, extension, and MCP in sync
Typed preset APIs at runtime

Self-host

Deploy your own instance

MagickMonkey is open source—you run it. There is no central hosted service: fork or clone, configure env vars from .env.example, and ship to your Vercel project (or any compatible host).

Deploy with Vercel

Deploys into your Vercel account · not our infrastructure

Your Vercel project

One-click creates a deployment under your account—not a shared MagickMonkey cloud.

Your credentials

Admin login, JWT secret, and storage tokens live in your env vars only.

Your script library

Connect your own script storage backend. You control access, rotation, and data residency.

Required env vars

GIST_IDGIST_TOKENACCESS_USERNAMEACCESS_PASSWORDJWT_SECRET
.env.exampleDeploy guideSource on GitHub

What you get

Three surfaces, one script library

Self-hosted open source—not a multi-tenant SaaS. MCP edits script source only; browser APIs come from the preset at runtime.

Author

Write userscripts in a full TypeScript editor with runtime typings, local drafts, and one-click publish to your private library.

  • Tabbed file tree & CodeMirror
  • URL rules panel
  • Optional Gemini AI rewrite
  • Editor dev mode for live preset testing

Deliver

Ship the same script library to Tampermonkey or a native Chrome extension—OTA updates, per-script toggles, and activation rules.

  • Auto-built launcher userscript
  • Extension: servers, scripts, rules, logs
  • Shared preset runtime APIs with full typings
  • Server & local activation rules

Automate

Let Cursor and other agents edit script files remotely via HTTP MCP or REST—without opening the web UI.

  • HTTP MCP for AI clients
  • REST CRUD with OpenAPI
  • Session cookie or API key auth
  • Search, patch, and validate remotely

Runtime pipeline

Library
Source of truth
Editor / MCP
Human or agent edits
Launcher / Extension
OTA shell
Preset
Shared runtime
Your scripts
Run in the page

Quick start

After deploying, configure, author, install, and integrate.

Your deployment · your credentials · your data
  1. 1

    Configure env

    Copy `.env.example`, set admin credentials and script storage keys, then redeploy if needed.

  2. 2

    Author

    Sign in to your instance, add `.ts` / `.js` modules in the editor, and configure URL rules when needed.

  3. 3

    Install

    Install the Tampermonkey launcher or load the Chrome extension ZIP from your editor.

  4. 4

    Integrate

    Optional: connect an MCP client or read the AI integration guide for agent setup.