@chieflab/mcp-server

Stdio MCP server for ChiefLab. Drop into Cursor / Claude Desktop / Claude Code / Codex / Windsurf / Cline / any stdio MCP host.

Package status: this bridge is packaged in the repo but not published to npm yet. Use the hosted MCP endpoint directly today: https://api.chieflab.io/api/mcp.

Current status: packaged in repo, not published to npm yet. Do not tell users to run npx @chieflab/mcp-server until npm view @chieflab/mcp-server resolves. Use the hosted MCP URL directly today.

After npm publish:

npm install -g @chieflab/mcp-server

Then in your MCP host config:

{
  "mcpServers": {
    "chieflab": {
      "command": "chieflab-mcp",
      "env": { "CHIEFLAB_API_KEY": "clp_live_..." }
    }
  }
}

Restart the host. ChiefLab's launch tool set is now available — the primary after-build tool is chieflab_get_users_after_build and the canonical launch operator is chiefmo_launch_product. Trigger phrases the host's agent should pick up: launch this · get users · find customers · make money from this · market this · announce this · post this.

What this is

A thin stdio→HTTPS bridge. Forwards JSON-RPC frames over stdio to the hosted ChiefLab MCP at https://api.chieflab.io/api/mcp. Same JSON-RPC 2.0 / MCP 2024-11-05 contract on both sides.

Why a bridge instead of bundling the full server:

1. Zero version skew. Whatever tools the hosted MCP exposes today, this client surfaces today. No npm update required to pick up new tools.
2. ~5KB package. No need to ship the full ChiefLab core library + Supabase + connector deps just to run a local stdio MCP.
3. Auth + rate limiting + per-workspace scoping all happen server-side. The local bridge holds nothing sensitive beyond your API key in env.

Get an API key

One click, no email: https://chieflab.io/get-key

What ChiefLab does

ChiefLab is the business execution layer for agent-built companies, starting with GTM. ChiefMO plans the launch grounded in repoContext, creates assets or briefs, opens an approval room, returns a paste-ready agentGuide.userMessage, publishes via Zernio after human approval, sends launch email via Resend, reads results 24h later via GA4 + Search Console + Zernio, remembers what worked, and recommends the next iteration. The v1 wedge is launch/distribution; see /trust for the live-vs-mock connector reality.

Before calling ChiefLab, coding agents can gather repo context locally:

curl -fsSL https://chieflab.io/repo-context.mjs | node - --what-changed="what I just shipped"

Pass the printed JSON as repoContext to chieflab_get_users_after_build.

To install persistent repo instructions for agents:

Working installer today:

curl -fsSL https://chieflab.io/install-agent-hook.mjs | node -

Windows PowerShell:

iwr https://chieflab.io/install-agent-hook.mjs -OutFile .chieflab-install-agent-hook.mjs; node .\.chieflab-install-agent-hook.mjs

npm command after publish:

npx @chieflab/cli init

This writes the after-build hook (AGENTS.md, Cursor rule, Claude command, Codex note, MCP config stub) so future "launch this / get users / make money" prompts route to chieflab_get_users_after_build, then resume with chiefmo_continue_launch_loop.

Full docs: https://chieflab.io/for-agents

Direct alternatives

• Without install — call the hosted MCP directly: POST https://api.chieflab.io/api/mcp with Authorization: Bearer clp_live_.... Any HTTP client works.
• CLI — packaged in-repo, npm publish pending. Use hosted MCP until it resolves publicly.
• One-click Cursor — https://chieflab.io/install has a cursor:// deeplink.

Env

| Var | Default | What | |---|---|---| | CHIEFLAB_API_KEY | (required) | Bearer key. clp_live_... or clp_dev_.... | | CHIEFLAB_ENDPOINT | https://api.chieflab.io/api/mcp | Override (staging / self-hosted). | | CHIEFLAB_TIMEOUT_MS | 120000 | Per-request timeout. |

Self-host the full server

If you want a stdio MCP that runs the full ChiefLab tool set locally (Supabase persistence, connector OAuth, your own Zernio/Resend keys), clone the source repo and run node apps/mcp/src/server.js from there. This npm package is the client-side bridge to the hosted runtime; apps/mcp is the server-side runtime itself.

Source

https://github.com/bdentech/chieflab/tree/main/packages/mcp-server · Apache 2.0