Keeper App Author

Build Keeper apps from Codex or Claude Code

Turn a plain-language operational brief into a complete Keeper app, or safely improve one that is already live. The plugin combines the current Keeper contract, focused composition guidance, and approval-gated deployment tools.

One public repository. Separate packages for Codex and Claude Code.

CodexClaude Code
01Read the live Keeper contract
02Build the complete app candidate
03Validate and show the diff
04Apply only after approval
05Open the deployed app

Definitions are reviewed separately from live-record changes.

Available today from MechaBee's public Git marketplace

This is an independent distribution channel for the current Codex and Claude Code packages. Keeper App Author is not yet published in OpenAI's universal Plugins Directory. The repository is public, versioned, and can be inspected before installation.

Installation

Choose the client you use

Add the MechaBee marketplace, install Keeper App Author, and complete MechaBee OAuth when your client prompts you to sign in.

Codex

Run these commands in a terminal with the Codex CLI available.

Codex install
codex plugin marketplace add MechaBee/keeper-authoring-plugins
codex plugin add keeper-app-author@mechabee

Complete OAuth when prompted, then start a new Codex task so the installed skills and Keeper tools are loaded.

Claude Code

Run these commands in a terminal with Claude Code available.

Claude Code install
claude plugin marketplace add MechaBee/keeper-authoring-plugins
claude plugin install keeper-app-author@mechabee

Complete OAuth when prompted, then start a new Claude Code session so the plugin is loaded.

Installing from Git gives the plugin the same skills, references, branded assets, and production Keeper MCP connection included in the versioned repository.

Authoring workflow

A complete path from brief to deployed app

The plugin does more than generate files. It discovers the correct workspace, reads the current contract, builds the candidate, and keeps the deployment reviewable.

Discover
Build
Validate
Diff
Approve
Open

Complete candidates

Create app metadata, schemas, views, navigation, workflows, providers, and agent actions required by the approved brief.

Contract validation

Validate the entire candidate against the live Keeper contract and resolve diagnostics before deployment.

Path-level review

Preview added, changed, and removed files before preparing the exact upload.

Approval-gated apply

Apply only the staged change you reviewed, with revision checks protecting against stale writes.

Safe app evolution

Inspect and repair existing apps while preserving their live records by default.

Direct launch

Open the deployed app from the launch URL returned after a successful apply.

Authentication and permissions

OAuth access stays scoped to your MechaBee account

The plugin connects to the production Keeper MCP server at mechabee.com and requests separate read and write scopes. It contains no credentials.

  • Read access discovers agents, workspaces, apps, contracts, and authorized definitions.
  • Write access validates, stages, and applies changes only within your available authority.
  • Raw-data access and replacement require the corresponding app permission and explicit user intent.
  • Passwords, access tokens, and MFA codes should never be pasted into a prompt.

What the review protects

Exact target

The agent and workspace are discovered before app operations begin.

Exact change

Prepared stages are bound to the reviewed diff and authorization.

Exact revision

Concurrency checks prevent a stale stage from silently overwriting newer work.

What you can build

Operational apps, not just starter screens

Keeper App Author can compose focused personal tools and multi-table team applications from the same declarative runtime.

Data and views

Schemas, relations, records, lists, tables, boards, dashboards, details, and forms.

Workflows

Record actions, automation steps, provider actions, and agent-assisted operations.

Access

Deny-by-default app policy, app roles, row-scoped data, and authenticated sharing.

Existing apps

Inspection, definition changes, migrations, validation repairs, and safe deployment.

Updates

Refresh the marketplace before reinstalling

Published Git releases keep the Codex and Claude Code packages on the same plugin version while allowing their manifests to evolve independently.

Codex update
codex plugin marketplace upgrade mechabee
codex plugin add keeper-app-author@mechabee
Claude Code update
claude plugin marketplace update mechabee
claude plugin install keeper-app-author@mechabee
Support

Installation, sign-in, and authoring help

Start with the checks below. If the problem continues, include your client, plugin version, and the non-sensitive error message when contacting MechaBee.

The plugin does not appear after installation+

Confirm the marketplace and plugin are listed in your client, then start a new task or session. Newly installed skills and tools are loaded at the start of a conversation.

OAuth did not complete+

Retry the sign-in prompt and finish it in the browser window opened by your client. Do not copy credentials into the conversation.

The plugin cannot edit an app+

Ask it to inspect the app's effective access. Definition edits, raw-data access, role changes, and data replacement require different Keeper capabilities.

A prepared deployment became stale+

Prepare the upload again and review the new diff. The plugin should never weaken the revision check or reuse a stale stage.

Give your coding agent a safe path into Keeper

Install from the public Git marketplace, sign in to MechaBee, and start with one real operational brief.