MCP server and Claude Code plugin

The growth team for what you just built

You ship from a terminal. Now the growth work starts there too. Hustlin runs as an MCP server, so Claude Code, Cursor and other coding agents can create the product, sync its context from the repo, generate the growth plan, show you the drafts, approve the ones you say yes to, and tell you what worked.

Nothing is posted, sent or spent without an approve. Accounts connect in the browser, never through the server.

Start free Pricing

Connect in two steps

A key is you: the same roles, approvals and activity log as the web app.

Create a key on hustlin.ai: open a product, then Settings → Advanced → Hustlin in Claude Code. The key is shown once.
In a terminal:
```
claude mcp add --transport http hustlin https://hustlin.ai/api/mcp --header "Authorization: Bearer hmk_…"
```
Any client that speaks Streamable HTTP works the same way with the URL https://hustlin.ai/api/mcp and a Bearer header.

Then ask: “launch this”, “what is waiting for approval?”, “what worked last week?”.

The Claude Code plugin

Skills that know the flow, plus playbooks that work before you have an account.

/launch reads the repo, writes HUSTLIN.md, creates the product, syncs context, plans, and shows the first week to approve.
/grow <goal> records a goal, refreshes the plan and picks the actions that serve it.
/approve walks through queued actions one at a time; approve, skip or edit each.
/report writes the what-worked report from real results, ready to save in the repo.
/launch also offers the conversion snippet: five lines in your signup handler, and every credited customer shows which channel brought them.
/launch-checklist and /directories are the playbooks Hustlin runs, usable with no account.

The plugin is in early access while the public listing is prepared. Email support@hustlin.ai for it; the MCP server above works today without it.

Tools

Each one wraps what the web app already does, with the same access rules.

Tool	Does	Writes
products	The products you can work on, your role on each, and the permission mode.	no
create_product	Add a product from its name, description and URL.	yes
sync_context	Push the HUSTLIN.md fields: ICP, pricing, voice and allowed claims, goals, funnel destination, mode.	yes
plan	Generate the growth plan and queue the first actions: listings, posts, a launch timeline, outreach and ad drafts.	yes
actions	The actions Hustlin drafted or ran, with status, channel, draft text and outcome.	no
approve	Approve, skip or edit one action. Approving runs it through your connected accounts.	yes
run	Run an already-approved action now, ahead of its slot. Leases, spend ceilings and platform policy apply; drafts are refused.	yes
results	Per channel: attempts, reach, credited signups, purchases, revenue; the learning loop's keep and stop lists.	no
report	The weekly what-worked report as markdown, ready to save as reports/YYYY-MM-DD-growth.md.	no
track_link	A short link for one channel. Clicks count per channel and the landing URL carries the visitor's tracking code.	yes
report_conversion	Report a signup, activation or purchase from your own product with the visitor's tracking code, so the channel gets the credit.	yes
conversion_snippet	The five lines for your signup handler (JavaScript, Swift, curl) and a venture key for them, shown once.	yes
connect	The browser URLs for connecting accounts and tracking. Connections never happen through the server.	no

HUSTLIN.md

The product context, in the repo, the way CLAUDE.md is the coding context.

# HUSTLIN.md

## Product
- name:
- url:
- description:
- stage: mvp            # idea | prototype | mvp | launched | growing
- funnel_destination:   # where tracked links send people

## Customers
- target_audience:
- pricing:

## Voice
# tone, words to use and avoid, claims allowed, claims never made

## Goals
- north_star:
- goals:
  -

## Mode
- mode: approve         # observe | approve | auto

## Hustlin
- product_id:           # filled by /launch
- conversion_key_prefix: # filled by /launch; the key lives in your deployment secrets

Only the fields you fill are changed on Hustlin. The agent pushes it with sync_context.

Permission modes

Set per product, in HUSTLIN.md or in Settings.

observe: Drafts only. Nothing leaves.
approve: The default. Every post, email, listing and ad waits for an approve, from the web app or from your terminal.
auto: Approved channels run under the daily spend ceiling you set on hustlin.ai. Platforms that forbid automated posting still wait for you.

Roles, limits and security

A viewer gets the read tools. An approver can approve, skip and edit. Only an owner can create products or change their settings. Every write from a key appears in the product’s activity log with the key’s name.

Keys are hashed at rest and shown once. Revoke any key from Settings → Advanced. A key cannot create or revoke keys. Calls are rate limited per key, and plan generation counts against the daily AI allowance of your plan.

Reads and planning are on every plan, including Free. Approving, running and autopilot need Growth or Studio, the same as the web app. See Trust and FAQ.