Sign inSign up

zeqqat

GitHub for your deterministic AI workflows.

Get started with one command

npx @zeqqat/mcp init

Works with Claude Code, Cursor, Hermes, and OpenClaw

Collections

Nothing is published yet. These are examples of what a collection looks like, not real records.

dokploy-ops

gaita/c/dokploy-ops@0.4.2DokployPostgresS3

Deploy, back up, restore and recover a Dokploy install without hand holding the agent through the API.

  • gaita/w/migrate-with-backup@2.1.0
  • gaita/w/restore-from-snapshot@1.3.0
  • gaita/c/postgres-safety@1.1.0
  • …and 5 more
8 items, each pinned to a version
gagaita1,204 runs

postgres-safety

gaita/c/postgres-safety@1.1.0PostgresS3

Every destructive Postgres operation wrapped in a snapshot and a compensating step.

  • gaita/w/safe-migration@3.0.1
  • gaita/w/point-in-time-restore@1.4.0
  • gaita/w/vacuum-and-report@1.0.0
  • …and 3 more
6 items, each pinned to a version
gagaita742 runs

cloudflare-edge

nia/c/cloudflare-edge@0.1.3CloudflareR2DNS

DNS cutovers, R2 bucket moves and cache purges that do not leave a half finished zone behind.

  • nia/w/dns-cutover@1.0.0
  • nia/w/r2-bucket-migrate@1.1.0
  • kip/c/purge-and-verify@1.0.1
  • …and 2 more
5 items, each pinned to a version
ninia96 runs

release-train

otieno/c/release-train@2.0.0GitHubnpm

Tag, changelog, npm publish and rollback, with the version bump as an explicit approval step.

  • otieno/w/cut-release@2.0.0
  • otieno/w/publish-npm@1.6.0
  • otieno/w/yank-release@1.0.0
  • …and 2 more
5 items, each pinned to a version
ototieno431 runs

supabase-ops

amina/c/supabase-ops@0.1.0SupabasePostgres

Branch, seed, diff and promote a Supabase project without an agent inventing a SQL migration.

  • amina/w/branch-and-seed@1.0.0
  • amina/w/schema-diff@1.2.0
  • amina/w/incident-snapshot@0.9.4
  • …and 1 more
4 items, each pinned to a version
amamina58 runs

coolify-ops

gaita/c/coolify-ops@0.2.0CoolifyDocker

The same recovery guarantees against a Coolify install. Same shapes, different API underneath.

  • gaita/w/coolify-deploy@1.1.0
  • gaita/w/coolify-backup@1.0.2
  • gaita/w/coolify-restore@1.0.2
  • …and 2 more
5 items, each pinned to a version
gagaita318 runs

How a run works, end to end

Version them, run them, share them, and read back exactly what your agent did.

01the command sets itself up

It finds the harnesses already on your machine and writes itself into each one. Nothing to configure by hand.

~/dev/app · zsh

02your agent searches before it improvises

Either the registry already has what you asked for, or your agent drafts it from the connectors you have. Both paths end in a declared workflow.

~/dev/app · claude code

03the run is waiting for you on zeqqat

Every step, its inputs and its timing, kept as a record you can hand to someone else.

zeqqat.com/runs/r_8fk2p
you / rotate-staging-keys / runs / r_8fk2p
you/rotate-staging-keysv0.1.0
passed18.4sclaude codea moment ago
start
01http0.9s
vault.read_current_key
02http2.4s
provider.create_key
03http1.1s
provider.verify_key
04http0.7s
vault.write_key
05http0.5s
slack.post_message
done

04you choose who else gets it

Public workflows are addressable by anyone. Private ones do not exist to anyone else.

zeqqat.com/you/rotate-staging-keys

Access for anyone.

Everyone else sees this:

you/rotate-staging-keysv0.1.0
1 run · 5 steps
start
01http
vault.read_current_key
02http
provider.create_key
03http
provider.verify_key
04http
vault.write_key
05http
slack.post_message
done

05group them, hand the whole set to your agent

A version bump inside a collection is an edit you make, never a surprise you inherit.

zeqqat.com/you/col/ops-kit
you / col / ops-kit
you/ops-kitv0.3.0
4 workflowsevery one pinned to a version
  • you/w/rotate-staging-keys@0.1.0private
  • you/w/deploy-preview@1.4.2public
  • gaita/w/migrate-with-backup@2.1.0public
  • amina/w/incident-snapshot@0.9.4public
mcp server
mcp.zeqqat.com/you/ops-kit

Your agent sees 4 tools, not the whole registry.

Apache-2.0