MereKit is a command-line interface (CLI) for Mere’s business apps.
Manage workspaces and websites yourself or through an AI assistant.
Use the mere command to explore an app’s
options, check your setup, and work with data you’re authorized to access.
Manage your business workspace, customer records, and team access in your browser.
Explore Mere Business ↗Use Mere apps from your terminal. Run commands yourself or connect an AI assistant.
Set up the CLI ↓Run AI models on your computer for tasks such as transcribing recordings. Requires separate setup and supported hardware.
Explore mere.run ↗mere apps list --json to see what’s installed.
Check an app’s help before running the examples.
Create and configure workspaces, check setup, and manage websites.
Manage finance profiles and automation with credentials scoped to each business.
Inspect websites, edit content and media, and manage publishing and revisions.
Manage projects, contacts, proposals, and reference material.
Configure AI assistants, inspect sessions, and manage shared links.
Manage scheduling, bookings, calendars, and meeting rooms.
Manage products, orders, checkout, and Stripe connections.
Manage meeting rooms, recordings, transcripts, and diagnostics.
Manage calls, text messages, phone numbers, and routing.
Manage mailboxes, conversations, drafts, and sending.
Manage donation campaigns, receipts, and payment settings.
Manage work apps, releases, publishing, and sharing.
Import recordings, create transcripts, and search local media.
Create and share delivery packages with password protection.
Define project relationships and access rules, then prepare shared context.
Create a workspace or inspect one you’re authorized to manage. These examples use placeholder names and IDs. Replace them with your own values and review confirmation flags before running commands.
# workspace lifecycle
mere business workspace create --name "Acme Studio" --slug acme-studio --yes --json
mere business workspace status --workspace ws_123 --json
mere business workspace setup --workspace ws_123 --json
Import a site, request a generated site, or upload HTML, CSS, JavaScript, and assets. Static uploads don’t run server code. Publishing changes the live site.
# existing site, generated site, or static bundle
mere business site import-existing --workspace ws_123 --url https://example.com --json
mere business site create --workspace ws_123 --business-name "Acme Studio" --json
mere business site bundle upload --workspace ws_123 --site-id site_123 --source-dir ./site-dist --json
mere business site bundle publish --workspace ws_123 --site-id site_123 --bundle-id sb_123 --environment live --yes --json
mere dynasite
commands for diagnostics, content revisions, and recovery. Follow the
website guide
for the required IDs and publishing steps.
mere link with MereKit or install the separate mere-link command.
Store project details and relationships in the mere.link.yaml file. Validate the file before using it to prepare context for people or assistants.
# install the separate Link package
npm install -g @merekit/link
# create and validate project configuration
mere-link config init --output mere.link.yaml
mere-link config validate --config mere.link.yaml --json
mere-link context inspect workspace workspace --role work --json
The mere link commands provide the same behavior as the separate Link package. The examples use placeholder workspace and operator IDs; replace them with values from your setup.
# use Link through MereKit
mere link generate workspace --workspace ws_123 --output mere.link.yaml --yes
mere link policy evaluate workspace workspace --capability project.context.export --operator approved-agent --json
mere link sync projects --config mere.link.yaml --json
mere link executor tools search "monday item" --json
Validate the configuration and export project context without changing external systems.
Review planned project records and links before applying changes.
Apply changes only after configuring access rules and reviewing the required confirmation flags.
After installing the CLI, use mere setup mere-run
to prepare the local AI software. Review the mere.run requirements
before starting.
# prepare mere.run for app use
mere setup mere-run --json
Download the models that the Media app uses for transcription and search.
To process your own recording, replace ./interview.m4a
with its file path.
# pull Media-requested local models
mere setup mere-run models --app media --json
# then process locally
mere media process ./interview.m4a --transcribe --embed
Use Mere Business to manage customer records, team access, and approvals in your browser. An AI assistant is optional; you can also run CLI commands yourself.
# open Mere Business in a browser (macOS)
open https://mere.business
Review the generated setup files before sharing them with your assistant. Start MCP with read-only tools. Enable write tools only when you intend to let your assistant change data. Each app’s permissions still apply.
# scaffold an agent kit for codex / claude
mere agent bootstrap --target codex
# expose to your agent runtime over MCP
mere mcp serve
# write tools, opted-in only
mere mcp serve --allow-writes
# prepare local AI runtime
mere setup mere-run --json
Finance credentials are scoped to a business profile. Check the selected profile before running commands.
MereKit doesn’t add --yes or --confirm on your behalf. Review each command’s confirmation requirements.
Use mere apps manifest to review an app’s command options and risk levels before running it.
# run in an interactive terminal npx --yes @merekit/cli@latest \ onboard --interactive # Node.js 24 or 25 and npm required
Enter an invite code to create a workspace, an email address to join the waitlist, or a workspace ID you’re authorized to use.
Joining the waitlist doesn’t create a workspace. Join in your browser if you don’t have an invite.
After workspace checks finish, open ONBOARDING.md in
~/.config/mere/agents/default/. Resolve any remaining setup requirements.