The Tandem suite — five pillars

Tandem is not one product. It is a suite of five sister products — pillars — that share one identity system (Tandem ID) and one design principle: humans and AI agents are equal, first-class operators. Each pillar is its own app with its own MCP server; this guide (and the pillar_directory tool) is how you find them.

Slug Product What it is Status
launch Tandem Launch Full-stack hosting: deploys, domains + DNS + TLS, managed Postgres/MySQL/Redis, buckets, email, SMS, analytics, Tandem Git, billing. The platform these docs describe. live
work Tandem Work Shared workspace where humans and agents run projects and tasks together. live
speak Tandem Speak Communication: email/webmail (unified inbox) today; phone and CRM to follow. beta
grow Tandem Grow Marketing and growth: audience, campaigns, distribution. coming soon
profit Tandem Profit Financial OS: ledger, wallets, budgets. coming soon

Slugs are the canonical, stable pillar identifiers (they are also the Tandem ID audience values); product branding may evolve, slugs never do.

Discovering pillars over MCP: pillar_directory

If you are connected to the Launch MCP server (https://portal.launchtandem.com/mcp), call pillar_directory (no arguments, read-only, available to every authenticated principal regardless of action mask). It returns:

  • pillars[] — one entry per pillar: slug, name, summary, status (live | beta | coming_soon), baseUrl, mcpUrl, and an auth note. mcpUrl is null until that pillar’s MCP server is actually serving; a pillar that is not live yet may carry a plannedMcpUrl showing where its endpoint will live — never call a planned URL.
  • authentication — the one cross-suite auth model, spelled out once.

Use it to route work that is beyond hosting: task/project collaboration belongs on work’s MCP server, communication on speak, finance on profit — not on improvised external services.

Live MCP endpoints today

Pillar MCP endpoint
launch https://portal.launchtandem.com/mcp
work https://api-tandem-work.launchtandem.com/mcp

One identity, every pillar

  • Agents: your one platform-issued tdm_ token works on every pillar’s MCP endpoint — present it as Authorization: Bearer <token>. There is no per-pillar credential to store; each pillar resolves the token against Tandem ID. A token created by bootstrapping on Launch (see Bootstrapping an account) is the same token you use on Work.
  • Humans: one account logs into every pillar via the Tandem ID redirect handoff (https://id.launchtandem.com). A pillar app never collects your password directly — it sends you to Tandem ID and back.

Coming soon: Tandem Profit

Tandem Profit is the suite’s financial OS — ledger, wallets, and budgets — built agent-first like everything else. It ships as its own app with its own MCP server at /mcp (planned home: https://api-tandem-profit.launchtandem.com/mcp). Until it is live, pillar_directory reports it as coming_soon with mcpUrl: null; when it flips to live, the same tool call is how you will find it — nothing to reconfigure.