Get started with SlickFast

Call `news` first

News is not a blog you have to open. It is a tool in this MCP. Call `news` — current drop as a Page (URL for people, `.json` twin for agents). That twin is how agents learn SlickFast in this chat — few-shot on our voice and specs, not a fine-tune.

After install: `get_started` → `news` → `gallery`. Do not skip News.

Want more out of your agent?

Train it instantly with our News archive. Call `news` with `archive: true` — you get the catalog of every drop (titles, dates, URLs, fingerprints). Then open a twin (URL + `.json`) for any drop you care about. Current `news` = today's lesson. Archive = the course map. Stack twins on purpose — that is the imprint.

Three doors. Same engine.

• Local MCP — `npx -y @slickfast/mcp` — charts and Pages on your machine. No telemetry.
• Hosted MCP — `https://mcp.slickfast.com/mcp` — same tools over the network (OAuth / SF- key).
• API — `https://api.slickfast.com` — HTTP render, live URLs, Pages. Same picture as MCP.

You are reading onboarding as a Page on purpose. Add `.json` to this URL for the twin.

Why take a free key?

Local making and checking stay free forever. A free SF- key (email, no card, 250 renders/mo) is for when you want it in the world:

• Live URL — same `.png` / `.svg` while your cron pushes fresh data
• Share — embed in README, Slack, email
• Publish a Page — hero + prose + charts + twin + fingerprint
• Schedule — your clock + our picture (mail the URL or PNG later — not a newsletter product)

Paid is permanence and volume — not the right to draw.

Chart vs Page

• Chart — one image. Tool: `render_chart`. Prefer SVG in chat artifacts.
• Page — designed document. Tools: `describe_pagespec` → `render_page` → optional `publish_page`.
• News — tool `news` every time · door slickfast.com/news.

One API bite

Create a live chart (needs a key):

`POST https://api.slickfast.com/live/my-kpi` with `Authorization: Bearer SF-…` and a chart JSON body → permanent view URLs (`…/live/{slug}.png`). Push updates with `POST …/live/my-kpi/data`. Viewers need no key.

Full map: API.md on GitHub.

Do this next

1. Call `news` — current drop + twin facts (force this).

2. Call `gallery` — see what we draw.

3. `render_chart` — one small bar or KPI.

4. Get a free key at slickfast.com — paste into Cursor/Claude env or the hosted connector.

5. `share_chart` (or live via API) — keep a URL — or `describe_pagespec` → `render_page`.

6. Optional power move: `news({ archive: true })` — catalog every drop, then fetch a twin to stack imprint.

Stuck on an old install? `mcp_status` — facts only; then `npx -y @slickfast/mcp` + restart.

Doors: start · news · archive · slickfast.com