mattsezgin/unofficial-clay-cli — explained in plain English
Analysis updated 2026-05-18
Manage Clay tables, fields, and enrichment runs from the terminal instead of the web app.
Ask a Claude Code skill to build a validated Clay table from a plain English request.
Test an enrichment on ten rows before scaling it up to a full table.
Share a working Clay workflow with the community as a leak proof template.
| mattsezgin/unofficial-clay-cli | abivan-tech/zvec-mcp | ardupilot/dronecan-webtools | |
|---|---|---|---|
| Stars | 9 | 9 | 9 |
| Language | JavaScript | JavaScript | JavaScript |
| Last pushed | — | — | 2025-09-02 |
| Maintenance | — | — | Quiet |
| Setup difficulty | moderate | moderate | moderate |
| Complexity | 3/5 | 3/5 | 3/5 |
| Audience | ops devops | developer | ops devops |
Figures from each repo's GitHub metadata at analysis time.
Requires a Clay account, workspace ID, and Node.js 20 or newer before running any commands.
This project is an unofficial command line tool for controlling Clay, a data enrichment and outreach platform, from your terminal instead of its web interface. It is not made or endorsed by Clay itself. It gives you about 50 commands covering tables, fields, enrichment runs, contact and company data sources, and full workbook exports. The tool can also be driven through an AI agent. It includes ten Claude Code skills that turn a plain English request, like asking for an email waterfall table, into a validated table specification and a small ten row test run, rather than jumping straight into a full live operation. There is also a community section where people can share working Clay setups as reusable templates and vote for the ones others find most useful, building a public leaderboard of contributors. Because the tool can spend your Clay credits and change your real data, it treats safety as a core feature rather than an afterthought. Every action that writes data requires a dry run first, followed by an explicit confirm step. Enrichment runs are capped at ten rows by default until you have checked the results, and writes are refused unless you have set the specific workspace and folder you intend to operate in. Sharing a workflow with the community is designed so your credentials cannot leak by accident. Instead of copying your raw configuration, a wizard rebuilds a clean template from it, you get to review exactly what will be published, and an automated check scans for anything resembling a real key, ID, or secret before anything goes live. Your authentication session is also stored outside the project folder so it cannot be committed to version control. Setting it up needs Node.js version 20 or newer, a Clay account with an email and password, and your Clay workspace ID, which you can find in your Clay app's URL. After installing dependencies and adding your credentials to a local environment file, a single read only command confirms everything is connected before you attempt any real writes.
An unofficial CLI and set of Claude Code skills for safely operating the Clay data enrichment platform from your terminal.
Mainly JavaScript. The stack also includes Node.js, JavaScript, Claude Code.
Use freely for any purpose, including commercial use, as long as you keep the copyright notice.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.