What exactly happens when Actuant “launches” my app?

An agent works through the launch checklist you'd otherwise do by hand: it writes your llms.txt, robots.txt and sitemap as a GitHub pull request, submits your app to 20 curated launch directories — filling each form live in a browser you can watch, and leaving the submit button to you. Anything that touches your code arrives as a pull request; nothing merges without your approval. Launch-copy drafting, analytics installed for you, and Stripe payments set up inside your app are on the roadmap, not shipped.

Does it work with my builder?

Yes. Actuant doesn't integrate with builders — it works on the app itself: the live URL, the GitHub repo, and your domain. If your app has a URL, Actuant can audit it; if it has a repo, Actuant can fix it. Lovable, Bolt, v0, Replit, Base44, Cursor, Claude Code, or hand-written all work the same way.

I've shipped five apps. Do I need five subscriptions?

No. One account covers your whole portfolio: the free plan covers 1 app, Launch covers 3, Portfolio is unlimited. Re-auditing an app you've already added is unlimited on every plan. The Signal dashboard that compares those apps side by side is still being built — today you get each app's audits, fixes and launch work in one place.

Will you spam directories with my half-finished app?

No. The audit runs first, and the agent only submits when your app clears the quality bar — that protects your launch and everyone else's. We maintain a curated list of directories that send real traffic, not a firehose of 400 link farms, and the agent never presses submit for you: it fills the form and hands the browser back.

What does the free plan actually include?

One app, unlimited re-audits of it, the full launch-readiness score and report with per-check fix guidance, and access to the MCP server for your coding agent. Agent runs are metered, and the free plan's usage is a one-time $5 of credit — roughly 16 deep audits — not a monthly allowance. Paid plans add a weekly usage allowance, monthly credit, and the agent doing the fixing and launching rather than just the diagnosing.

Can I share a report with someone else?

Not yet. Reports live in your dashboard behind your login today; public, shareable report links are on the roadmap. Anything on this site marked “coming soon” isn't built — we'd rather you buy the plan for what it does now.

Agents & MCP

Actuant for agents: the MCP server

Actuant exposes its launch-readiness audit over the Model Context Protocol so agents like Claude Code, Cursor, and Codex can audit apps, read reports, and fix findings as tool calls.

Last updated 2026-07-19

Actuant ships a remote MCP server at https://www.actuant.dev/api/mcp (Streamable HTTP). Connect any MCP-native agent and it can run audits, read reports, and interpret launch-readiness for you without leaving your editor or terminal.

Why drive Actuant from an agent

Your agent already has your codebase open — it can read a finding and fix it in the same session, then re-run the audit to watch the score climb.
No context-switching to a dashboard: audit, interpret, fix, verify, all in the loop.
The agent identifies itself during OAuth, so Actuant knows whether it's Claude Code, Codex, or Cursor asking.

Authentication in one line

There are no API keys to paste for the standard flow. On first connect, your browser opens Actuant, you sign in, and you approve a consent screen that names the requesting agent. Tokens live on your machine and can be revoked in Settings → Agents & MCP.

Headless option

For headless/CI where a browser can't open, mint a manual bearer key (act_…) in Settings and pass it as an Authorization header instead.

Keep reading

Connect an agent

Step-by-step: add the Actuant MCP server to Claude Code, Cursor, VS Code, or Codex CLI, complete the OAuth sign-in, and verify all 13 tools are available.

Tools reference

The complete Actuant MCP tool list: eight free tools (scan_app, get_scan, audit_app, get_audit, list_apps, scan_history, explain_check, get_account) and five plan-gated tools for the Launch and Portfolio plans.

API keys

For headless environments and CI where a browser can't open for OAuth, mint a manual bearer API key in Settings and pass it as an Authorization header to the Actuant MCP server.