ChiefLab is a remote MCP server that gives an AI agent 45 tools, among them chieflab_approve_action, chieflab_boot, chieflab_brain_summary. It answers at https://api.chieflab.io/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 5 September 2026; the last check, on 18 October 2026, succeeded.
Open execution contract for agents doing business work. 6 operators, one MIT-licensed spec.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
chieflab_approve_action | [chieflab_* alias of chiefmo_approve_action] Approve one ChiefMO publish/send action so its executor can fire. USE WHEN the user — in IDE chat — said 'approve <channel>' (e.g. 'approve linkedin', 'approve hn'), 'approve all', 'ship it', 'go Inputs: actionId, id, autoExecute, platforms, mediaUrls, recipients |
chieflab_boot | Alias of chieflab_status. Use as the FIRST tool when an agent session starts on a workspace that already has activity — recovers all open business loops with literal user commands. Same response shape as chieflab_status, same handler. If th Inputs: workspaceId, currentRepoContext, projectName |
chieflab_brain_summary | USE WHEN the user asks 'what do you remember about my brand?' / 'show me my brain' / 'what have you learned?'. Returns a plain-English paragraph summarizing what the per-workspace brain has accumulated: launch count, top-performing channels Inputs: tenantId, workspaceId |
chieflab_check_measurement_due | P71 — measurement queue inspector. USE WHEN the agent wants to know which executed actions are ready for their 24h readback (regardless of how they were executed — native connector OR manual paste). Lists actions where metadata.proof.measur Inputs: workspaceId, runId |
chieflab_connect_provider | Connect a third-party provider (Zernio, Resend, GA4, Search Console, HubSpot, Stripe, Linear, Notion, Slack) to this workspace. USE WHEN the user wants to wire up publishing, email sending, or analytics readback. For OAuth providers (ga4 / Inputs: provider |
chieflab_connector_status | USE WHEN the user just completed a connector OAuth flow and you want to confirm it succeeded — 'did my connection work?', 'is my Zernio/HubSpot/Stripe connected?'. Returns status: pending | connected | failed for the given connectionId. Inputs: connectionId, workspaceId |
chieflab_continue_launch_loop | [chieflab_* alias of chiefmo_continue_launch_loop] Resume a ChiefLab launch loop from runId. USE WHEN an agent has already called chieflab_get_users_after_build / chiefmo_launch_product and needs the exact next action: surface reviewUrl, ex Inputs: runId, workspaceId, responseShape, includeFullArtifacts |
chieflab_create_next_move_action | P75 — turn a Next Move suggestion into an approval-gated draft action. USE WHEN you've called chieflab_suggest_next_move and the suggestion's kind is not 'wait' or 'noop'. Creates an actionStore entry with status='awaiting_approval', the su Inputs: runId, channel, metrics, workspaceId |
chieflab_create_work_request | USE WHEN your operator hits a gap it can't fulfill itself and wants to route the work to another operator — 'I need a demo video for this launch', 'request design help for the hero image'. Creates an open work request that other operators c Inputs: capabilityNeeded, brief, sourceRunId, sourceOperatorId, budget, deadline |
chieflab_execute_approved_action | P71 — closed-loop executor wrapper. USE WHEN chiefmo_approve_action just succeeded on an action whose executionMatrix.mode is oauth_connector or api_key_connector AND connectorReady is true. Routes to the right native executor (chiefmo_publ Inputs: actionId, platforms, mediaUrls, recipients, subject, workspaceId |
chieflab_force_measurement_due | P93 — admin escape hatch. Forces a proof_ledger row's measurement_due_at into the past so the cron's next tick picks it up. USE WHEN smoke testing the launch → measure → next-move chain without waiting 24h, OR an ops user needs to retry a s Inputs: proofId, dueAt, adminToken |
chieflab_get_capability | USE WHEN you have a specific operatorId + capability and want the full machine-readable profile (inputs, outputs, pricing, approval-required flag, endpoint). Pre-flight check before chieflab_create_work_request. Inputs: operatorId, capability |
chieflab_get_company_profile | P88 — read the workspace's stored company profile. Returns { profile, source, confidence, updated_at }. Use before launch to confirm what ChiefLab will ground in. Inputs: workspaceId |
chieflab_get_publishing_targets | P79 — read the workspace's stored publishing target defaults. Returns { channelTargets, store }. Useful before launch so the agent can surface 'You haven't connected an Instagram account yet — set it via chieflab_set_publishing_targets' ins Inputs: workspaceId |
chieflab_get_users_after_build | Outcome-named alias for chiefmo_launch_product. USE WHEN a coding agent just built, shipped, or deployed something and the user asks 'get users', 'find customers', 'make money from this', 'get paying users', 'get eyes on this', 'what now?', Inputs: productUrl, productDescription, goal, channels, repoContext, brand |
chieflab_help | FIRST TOOL — call before anything else when you don't know what ChiefLab does or where to start. Returns the operator menu + workspace state (connectors wired, last run, signup status) + the single next action for this workspace. Cheap, no |
chieflab_inbox | USE WHEN the user asks 'what came in from my launches?' / 'show me my replies' / 'what's in my inbox?' / 'who responded to the LinkedIn post?'. Returns engagement events for THIS workspace, ordered by recency. Filter by status (new / drafte Inputs: status, sinceHours, limit, workspaceId |
chieflab_launch_product | Operator: chieflab-launch (primary). Spec v0.1 reference implementation of the orchestrator. End-to-end launch loop: repo-grounded positioning + per-channel drafts (linkedin, x, hn, reddit, email, landing_hero, product_hunt) + image briefs Inputs: productUrl, goal, channels, brand, repoContext, imagesNeeded |
chieflab_list_specialists | P87 — list the specialist agents ChiefLab can delegate to (design / video / research / outreach / seo / analytics). USE WHEN the user asks 'what can ChiefLab do beyond launch posts?' or before calling chieflab_request_specialist. Returns th |
chieflab_mark_action_done | P135 — mark a next-move action as completed when the founder has done the move BUT there's no URL to record (e.g. reply_to_commenters, dm_engagers, mark replies done). Flips the action to executed with metadata.markedManuallyAt + metadata.e Inputs: actionId, note, workspaceId |
chieflab_measure_hacker_news | P109 — pull a Hacker News post's score + comments + top replies via the public HN API and write them to the action's metadata.proof. USE WHEN a published Hacker News action is ripe for 24h measurement (checks the publishedUrl on the action, Inputs: actionId, force, workspaceId |
chieflab_measure_reddit | P115 — pull a Reddit post's score + comments + upvote ratio + top replies via the public Reddit JSON API and write them to the action's metadata.proof. USE WHEN a published Reddit action is ripe for 24h measurement. Parses subreddit + post Inputs: actionId, force, workspaceId |
chieflab_persistence_health | P91 — verify the persistent stores. Probes proof_ledger / publishing_targets / company_profiles tables (Supabase) OR confirms the in-memory fallback. USE WHEN the user just ran the SQL migrations and wants to confirm the API is now using du Inputs: workspaceId |
chieflab_post_launch_review | [chieflab_* alias of chiefmo_post_launch_review] USE WHEN ≥24h has passed since chiefmo_publish_approved_post fired and the user asks 'how did the launch perform?', 'what worked?', 'metrics from my launch'. Closes the loop: pulls 24h+ engag Inputs: runId, accountIds, lookbackDays, outputMode |
chieflab_prepare_next_move | [chieflab_* alias of chiefmo_prepare_next_move] USE WHEN the user has just published a launch (or ≥24h post-launch) and asks 'what's next?', 'follow-up post?', 'iterate on this', 'plan day 2'. P13 — turns one launch into a 7-day launch mode Inputs: runId, horizon, channels, workspaceId |
chieflab_publish_approved_post | [chieflab_* alias of chiefmo_publish_approved_post] Publish an approved social post (LinkedIn / X / Threads / Instagram / Facebook / Bluesky / TikTok) through the social publishing rail (current adapter: zernio). USE WHEN the user has appro Inputs: actionId, content, platforms, mediaUrls, scheduleAt |
chieflab_query_proof_ledger | P80 — query the persistent proof ledger. USE WHEN the user (or a dashboard) asks 'what has ChiefLab actually shipped for this workspace?' or 'show me the launch history.' Returns the proof rows for executed publishes / sends / manual-posts Inputs: workspaceId, runId, sinceTimestamp, limit, measurementDueOnly |
chieflab_record_manual_metrics | P116 — paste-what-you-see metric fallback for channels without public-API measurement (X, LinkedIn, Email, landing pages, Product Hunt). USE WHEN a published action's channel doesn't have a public-JSON metrics endpoint (anything except hack Inputs: actionId, metrics, force, workspaceId |
chieflab_record_manual_publish | USE WHEN the user has manually posted to a channel returned by chieflab_use_manual_fallback (Product Hunt / HN / Reddit / Discord / etc.) and wants to feed the live URL back to ChiefLab so the closed loop continues. Records the URL on the o Inputs: actionId, publishedUrl, publishedAt, notes, workspaceId |
chieflab_redraft | USE WHEN the user says 'make this more casual' / 'shorter' / 'less salesy' / 'add a specific number' / 'redraft this' about a published draft. Pulls the existing brief for the actionId, merges the instruction, returns an updated brief your Inputs: actionId, instruction, body, workspaceId |
chieflab_regenerate_visual_asset | P72 — regenerate a single visual asset (LinkedIn graphic, X graphic, landing hero, etc.) with a different style / fidelity / headline / model. USE WHEN a reviewer hits 'Regenerate' on a launch image in the Launch Room. Reads the original la Inputs: runId, channel, assetId, style, fidelity, headline |
chieflab_request_specialist | P87 — delegate to a specialist agent. USE WHEN the launch needs more than copy: a graphic brief (kind='design'), a demo video shot list (kind='video'), a prospective-customer research plan (kind='research'), personalized outreach drafts (ki Inputs: kind, brief, runId, autoCreateAction, workspaceId |
chieflab_retry_blocked_action | P13 — re-check a blocked publishAction's connector readiness. Returns whether the channel is now ready (so the agent can re-fire chiefmo_publish_approved_post / chiefmo_send_approved_email) or still blocked with the up-to-date connect path. Inputs: actionId, workspaceId |
chieflab_review_visual_asset | P104 — approve or reject a single visual asset (LinkedIn graphic / X image / landing hero / Product Hunt gallery / carousel slide). USE WHEN a reviewer hits 'Approve' or 'Reject' on a launch image in the Launch Room. Reads the run's stored Inputs: runId, assetId, decision, reason, workspaceId |
chieflab_search_capabilities | USE WHEN your operator needs a capability outside its own scope and wants to find another operator that can fulfill it — 'find me a demo-video capability', 'who can do SEO audits', 'search for design help'. Returns active capability records Inputs: capability, tags, limit |
chieflab_send_approved_email | [chieflab_* alias of chiefmo_send_approved_email] Send an approved launch email through the email sending rail (current adapter: resend). USE WHEN the user has approved an email publishAction from chiefmo_launch_product and you need to fire Inputs: actionId, from, to, subject, html, text |
chieflab_set_company_profile | P88 — set the workspace's persistent company profile. ChiefLab's pre-P88 brief pipeline was repo-first; without a repo, launches landed thin. P88 lets the founder (or an agent) store the company / product facts ONCE and every subsequent lau Inputs: workspaceId, profile, source, confidence |
chieflab_set_provider_key | Store a provider API key for THIS workspace. Once stored, ChiefLab uses your key (BYOK — you pay the provider directly, no markup). Without it, ChiefLab uses its own key and bills through with a margin. Providers: gemini (image gen), resend Inputs: provider, apiKey, workspaceId |
chieflab_set_publishing_targets | P79 — set per-workspace publishing target defaults so chiefmo_approve_action({ autoExecute: true }) doesn't need the agent to pass platform / recipient ids on every call. One-time setup per workspace. channelTargets is a map { linkedin: { a Inputs: workspaceId, channelTargets |
chieflab_signup_workspace | USE WHEN the user has no ChiefLab API key yet and you've gotten a 401 / 'authentication required' error from any other tool. Agent-first signup: creates a new workspace and returns the API key inline as `apiKey`. PREFERRED flow: use your fi Inputs: workspaceLabel, contactEmail, agentName |
chieflab_skip_next_move, chieflab_status, chieflab_suggest_next_move, chieflab_use_manual_fallback, chieflab_verify_install
Every block below points at https://api.chieflab.io/api/mcp. Pick your client and copy.
claude mcp add --transport http chieflab https://api.chieflab.io/api/mcp
{
"mcpServers": {
"chieflab": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.chieflab.io/api/mcp"]
}
}
}{
"mcpServers": {
"chieflab": {
"url": "https://api.chieflab.io/api/mcp"
}
}
}{
"servers": {
"chieflab": {
"type": "http",
"url": "https://api.chieflab.io/api/mcp"
}
}
}{
"context_servers": {
"chieflab": {
"url": "https://api.chieflab.io/api/mcp"
}
}
}{
"mcpServers": {
"chieflab": {
"serverUrl": "https://api.chieflab.io/api/mcp"
}
}
}{
"mcpServers": {
"chieflab": {
"url": "https://api.chieflab.io/api/mcp"
}
}
}name: ChiefLab
version: 0.0.1
schema: v1
mcpServers:
- name: ChiefLab
type: streamable-http
url: https://api.chieflab.io/api/mcp{
"mcpServers": {
"chieflab": {
"httpUrl": "https://api.chieflab.io/api/mcp"
}
}
}{
"mcpServers": {
"chieflab": {
"type": "http",
"url": "https://api.chieflab.io/api/mcp"
}
}
}{
"mcpServers": {
"chieflab": {
"url": "https://api.chieflab.io/api/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fapi.chieflab.io%2Fapi%2Fmcp&type=streamable_http&id=chieflab&name=ChiefLab
It answered our last check on 18 October 2026 in 210 ms. Over 10 checks since 5 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
45, as returned by the server's own tools/list on 31 August 2026: chieflab_approve_action, chieflab_boot, chieflab_brain_summary, chieflab_check_measurement_due, chieflab_connect_provider, chieflab_connector_status, chieflab_continue_launch_loop, chieflab_create_next_move_action, and 37 more.
It answered our last check on 18 October 2026 in 210 ms. Over 10 checks since 5 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://api.chieflab.io/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.bdentech. Endpoint host: api.chieflab.io. ARD identifier: urn:air:io.github.bdentech:mcp:chieflab.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.