Skip to content
stack
Install
Pre-alpha · v0.1

The control plane for your entire dev stack.

Every npx create-next-app is followed by an hour of tab-hopping — create a Supabase project, copy Vercel tokens, paste Sentry DSNs, add MCP servers to .mcp.json. Stack collapses that hour into one command.

$ curl -fsSL stack.ashlr.ai/install.sh | bash
Get started GitHub
23 providers · 5 templates · 17 MCP tools · one command
~ / projects / raven — stack
§ 01 · Thesis
The one-command moment

Forty-five minutes, or one command.

What wiring a single service actually looks like — before and after. Flip the tab.

1. Create Supabase project (browser)

→ open supabase.com/dashboard → new project
→ pick region, wait ~60s for provision
→ settings › api › copy URL + anon + service_role

2. Paste keys into .env.local

$ vim .env.local
NEXT_PUBLIC_SUPABASE_URL=https://abc123.supabase.co
NEXT_PUBLIC_SUPABASE_ANON_KEY=eyJhbGci…
SUPABASE_SERVICE_ROLE_KEY=eyJhbGci…

3. Install client

$ bun add @supabase/supabase-js

4. Wire up MCP server by hand

$ vim .mcp.json
{ "mcpServers": { "supabase": {
"command": "npx",
"args": ["-y", "@supabase/mcp-server-supabase"],
"env": { "SUPABASE_ACCESS_TOKEN": "???" }
} } }

5. Generate personal access token (browser)

→ supabase.com/dashboard/account/tokens
→ copy, paste into .mcp.json, swear a little

6. Lint your .env out of git history (just in case)

⚠ you've done this part wrong before
$ git log -p | grep SERVICE_ROLE… # please no

7. Restart Claude Code, pray MCP attaches

→ quit. relaunch. squint at logs.

8. Realize you forgot to add Sentry, Resend, PostHog…

repeat steps 1–7, seven more times
45 minutes·Context-switches: 12·Secrets pasted into plain text: at least 3
§ 03 · In motion

See it run.

Not a recording — a faithful, looping replay of the real CLI. Initialise, add a provider, run the app. The whole loop is under thirty seconds.

§ 02 · Providers · 26

Every service that hits your .env — curated.

One hand-tuned adapter per provider — OAuth dance, resource creation, secret slots, MCP wiring — all declarative. Missing one? Adapters are pluggable; write yours in a weekend.

Database

06
  • MCP stack add
    Supabase · OAuth
    Postgres + Auth + Storage
  • MCP stack add
    Neon · PAT
    Serverless Postgres
  • stack add
    Turso · PAT
    Edge SQLite (libSQL)
  • stack add
    Convex · API key
    Reactive backend-as-a-service
  • stack add
    Upstash · API key
    Serverless Redis + Kafka
  • stack add
    Firebase · Service key
    Realtime DB + Auth

Deploy

06
  • MCP stack add
    Vercel · PAT
    Frontend platform
  • stack add
    Railway · API key
    Infra from a repo
  • stack add
    Fly.io · API key
    VMs at the edge
  • MCP stack add
    Cloudflare · PAT
    Workers, R2, D1
  • stack add
    Render · API key
    Zero-config hosting
  • stack add
    Modal · API key
    Serverless GPU + sandbox

Cloud

01
  • stack add
    AWS · API key
    S3, Lambda, RDS

AI

06
  • stack add
    OpenAI · API key
    GPT, Realtime, embeddings
  • stack add
    Anthropic · API key
    Claude models + MCP
  • stack add
    xAI · API key
    Grok + tool use
  • stack add
    DeepSeek · API key
    Open-weight models
  • stack add
    Replicate · PAT
    OSS model inference
  • stack add
    Braintrust · API key
    LLM evals + observability

Analytics

01
  • MCP stack add
    PostHog · API key
    Product analytics + flags

Errors

01
  • MCP stack add
    Sentry · PAT
    Error + performance tracking

Payments

01
  • MCP stack add
    Stripe · API key
    Billing, subscriptions, tax

Code

01
  • MCP stack add
    GitHub · Device
    Repos, Actions, OAuth

Tickets

01
  • MCP stack add
    Linear · API key
    Issues, projects, cycles

Email

01
  • stack add
    Resend · API key
    Transactional + React email

Auth

01
  • stack add
    Clerk · API key
    Drop-in auth + users

Brand marks provided by simple-icons and used for identification. All trademarks are property of their respective owners.

§ 04 · Mechanics

Three surfaces, one source of truth.

Stack coordinates the CLI, the vault, and your project files so every dev on a repo — and every agent with access — sees an identical stack.

  1. 01

    CLI orchestrates

    You run stack add. The CLI drives the provider OAuth, creates the upstream resource, and picks sane defaults — region, plan, project name — from your repo.

    $ stack add supabase
    → browser · OAuth
    → create project raven-prod
    → fetch service keys
  2. 02

    Phantom stores

    Every secret is written through Phantom Secrets. Stack never holds the values — it holds the slot names and lets Phantom do the vault work.

    $ phantom status
    vault: ~/.phantom · E2E encrypted
    + SUPABASE_URL
    + SUPABASE_SERVICE_ROLE_KEY
  3. 03

    Wired everywhere

    Stack patches .env.local, .mcp.json, and .stack.toml. Your dev server, editor, and Claude Code all see the same stack.

    $ stack exec -- bun dev
    env injected via phantom proxy
    mcp: supabase attached
    ready in 812ms
§ 05 · Starter Stacks · 05

Opinionated starters, wired end-to-end.

Each template is a real stack — not a boilerplate dump. stack init runs every provider's OAuth, provisions resources, stores secrets in Phantom, and hands you a repo that bun devs in thirty seconds.

Don't see your stack? stack init opens an interactive picker.
Claude Code integration

Your agent can run Stack directly.

Stack ships as a Claude Code plugin and an MCP server. From chat, call /stack:add and Claude provisions the service, stores secrets in Phantom, and re-wires your .mcp.json — no copy-paste back to the terminal.

  • ▸
    MCP-native
    Every Stack command is exposed as an MCP tool.
  • ▸
    Plugin commands
    /stack:add, /stack:doctor, /stack:open — all available in-chat.
  • ▸
    Phantom-gated
    Secrets are read through Phantom's proxy. The agent sees a slot name, never a key.
# one-time setup
$ claude plugin install ashlr-ai/stack-plugin
◇Claude Code·raven
›
Ask Claude anything…
⌘ K
§ 06 · Works with your agent

Every MCP-capable agent, out of the box.

Stack's MCP server drops into Claude Code, Cursor, Windsurf, Codex, or ashlrcode with the same .mcp.json. Your agent learns 17 new tools — stack_add, stack_scan, stack_doctor, and the rest — and can wire any of the 23 providers for the user without leaving chat.

Protocol: Model Context Protocol · modelcontextprotocol.io · 17 tools · 3 resources · stdio + SSE
§ 07 · The Ashlr Constellation

Four tools. One coherent platform.

Stack is the control plane. Phantom is the vault. ashlr-plugin is the context compressor. ashlrcode is the multi-model runtime. They compose — none of them require the others, but together they're load-bearing.

▲ Control plane
Stack

The CLI + MCP that provisions, wires, and operates every service.

◇ Vault
Phantom Secrets

E2E-encrypted secret storage. Stack writes every credential through Phantom.

◈ Context compressor
ashlr-plugin

Drops Claude Code token spend ~80% on large repos with genome-indexed read/grep.

◎ Multi-model CLI
ashlrcode

Route the same prompt across Claude, GPT, Grok, DeepSeek. Compare, diff, stream.

→ Stack writes through Phantom → ashlr-plugin shares the same .stack.toml → ashlrcode respects the same secret slots