ChiefLab

@bdentech

About ChiefLab

Open execution contract for agents doing business work. 6 operators following one spec. Approval-gated, tenant-isolated, MIT. Reference at chieflab.io/spec/v0.1.

#gtm #launch #approval-gated #closed-loop #repo-aware #open-spec #marketing #agent-infrastructure #mcp-server

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "chieflab": {
      "url": "https://api.chieflab.io/api/mcp",
      "headers": {
        "Authorization": "Bearer clp_live_<your-key>"
      }
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is ChiefLab?

ChiefLab is an open execution contract for AI agents performing business tasks. It provides a set of operators that handle the entire lifecycle from drafting to measurement, ensuring actions are approved, idempotent, and tenant-scoped. It is designed for stateless LLMs to offload operational work such as OAuth, approval gates, measurement polling, and memory persistence.

How to use ChiefLab?

Install ChiefLab as a hosted HTTP MCP server using Claude Code with a single command: claude mcp add --transport http chieflab https://api.chieflab.io/api/mcp --header "Authorization: Bearer <your-key>". Once connected, agents can invoke any of the six conformant operator tools (e.g., chieflab_launch_product, chieflab_post, chieflab_measure) to execute business tasks through the prepare → review → approve → execute → measure → remember lifecycle.

Key features of ChiefLab

Six live operators covering the full business lifecycle.
Approval-gated actions enforced server-side.
OAuth token handling for external connectors.
24h post-launch measurement (GA4, Search Console, etc.).
Tenant-scoped memory for brand voice and facts.
Idempotency guaranteed under retry.

Use cases of ChiefLab

End-to-end product launch (post, email, landing, measure) in one run.
Publishing a single-channel post with review and approval gates.
Sending approval-gated emails via Resend.
Retrieving 24‑hour post-launch engagement metrics.
Reading tenant-scoped memory for consistent brand voice and proof assets.

FAQ from ChiefLab

What is the ChiefLab lifecycle?

Operators follow the sequence: prepare → review → approve → execute → measure → remember.

How do I install ChiefLab?

Use Claude Code: claude mcp add --transport http chieflab https://api.chieflab.io/api/mcp --header "Authorization: Bearer <your-key>".

What operators are available?

Six live operators: chieflab-launch (orchestrator), chieflab-post, chieflab-email, chieflab-measure, chieflab-brain (memory), and chieflab-connect (OAuth flow).

Does ChiefLab guarantee idempotency?

Yes. The operator contract guarantees idempotency under retry for all operations.

Where is data stored?

Tenant-scoped memory is persisted by the chieflab-brain operator, and measurement data is polled from external APIs (GA4, Search Console, Zernio) 24 hours after launch.

Frequently asked questions