Products

Ships to

Muse connectors

Get your product into Muse, and every other assistant.

Muse, Meta’s personal AI agent, does tasks across people’s apps through connectors. Build your product’s tools once in Flow and have them ready for Muse, ChatGPT and Claude.

Muse’s connector program is in review-based early access. Facts here are from Meta’s announcements and press coverage.

What you can build

Be the app Muse reaches for
when someone asks.

Shopping

Muse buys, your store sells

Shopping and payments were among Muse’s launch connectors (Shopify, Walmart, Sephora, Best Buy, Stripe, PayPal). A connector puts your catalogue and checkout in that flow.

Travel

Trips planned end to end

Search, hold and book from one request.

Food

Dinner sorted

Reservations and delivery on request.

Productivity

Work done across apps

Notes, docs and tasks updated for the user.

Brand examples are illustrations of what could be built, not those companies' products.

The usual way vs. Flow

Every assistant wants its own integration.
Flow makes one serve them all.

Building it yourself~6 weeks

  1. Apply and wait for Muse review varies
  2. API or MCP server for Muse 1 week
  3. User sign-in and scopes 1–2 weeks
  4. Again for ChatGPT 1 week
  5. Again for Claude 1 week

Muse has published no SDK yet; a firsthand report says its form takes a live API or a hosted MCP server (unconfirmed).

With Flow Frameworkan afternoon

  1. Create the project1 min
  2. Write your tools1–2 hrs
  3. Serve as MCP with sign-inbuilt in
tools/free-slots.ts
import { tool } from "@flow-engineer/flow";
import { z } from "zod";

export default tool({
  name: "free_slots",
  description: "List open tables for a party size and time.",
  input: z.object({ when: z.string(), guests: z.number() }),
  run: async (q) => api.tables.available(q),
});

How Flow works

Write it once. Ship it to Muse and everywhere else.

  • Tools become your appThe same typed tools are served as an MCP server and a CLI. No transport, schema or protocol code.
  • Each user signs inFlow handles each user’s sign-in, so the assistant only reaches what that person can.
  • Tested and tracedSimulated users check which prompts should and should not call your tools, and every call is traced.

Get started

How to get ready for Muse with Flow.

  1. Create a Flow project

    Run npx @flow-engineer/flow new my-agent, or ask Claude Code or Codex to set it up. You get one folder: the agent’s instructions, its tools, its skills and its tests.

  2. Write what it can do as tools

    Each job is a TypeScript function with a typed input that calls your API: check an order, book a slot, find a deal. No protocol code.

  3. Test it on simulated users

    Run npx @flow-engineer/flow test. Simulated users try the scenarios that matter, including people who change their mind or ask for something your agent should refuse.

  4. Serve it with sign-in

    Flow serves your tools as an MCP server on HTTPS with each user’s sign-in, which is what assistants like ChatGPT and Claude connect to today.

  5. Apply to Muse

    Apply through Meta’s Muse connector program with your live server. Meanwhile the same project is live in ChatGPT and Claude.

terminal
$ npx @flow-engineer/flow new my-agent
$ cd my-agent
$ npx @flow-engineer/flow test
✓ 24 scenarios passing

Guide

Muse and Muse connectors, explained.

What is Meta Muse?

Muse is Meta’s personal AI agent, launched on 8 September 2026 and running on Meta’s Muse Spark model. It connects to a person’s apps, such as email and calendar, and carries out tasks across their accounts.

What are Muse connectors?

Connectors are how Muse reaches other products. Meta describes two kinds: directory connectors that developers submit and Meta reviews, and custom connectors that Muse sets up for a single user. Meta said over 1,500 developers applied in the program’s first week.

How do I build a Muse connector?

Apply through Meta’s connector program; Meta reviews each submission for function, security and legal requirements and tests it end to end. Meta has not published an SDK, fees or review times. Having a working, signed-in API or MCP server ready is the practical first step, and it also gets you into ChatGPT and Claude.

Does Muse support MCP?

Not officially confirmed. Meta’s Connect recap describes connecting via an API or an MCP server, and one firsthand report says the form accepts a hosted MCP server. We will update this page when Meta publishes docs.

Which brands are on Muse?

Launch partners reported by TechCrunch include Stripe, Shopify, Shop Pay, PayPal, Best Buy, Gap, Sephora, Walmart, Wayfair, Expedia, GitHub, Granola and Notion, with Instacart coming.

Does Muse take a cut?

Meta has said Muse will be free for a large number of tokens and plans to earn a small fee on transactions.

FAQ

Muse questions,
answered.

What is Meta Muse?

Meta’s personal AI agent, launched 8 September 2026. It connects to a person’s apps and does tasks across them.

How do I build a Muse connector?

Apply through Meta’s Muse connector program, which reviews and tests each submission. Have a live API or MCP server with user sign-in ready; Flow builds that from your tools.

Is there a Muse SDK or API?

Meta has not published one as of October 2026.

Does Muse support MCP?

Not officially confirmed. Meta’s materials mention connecting via an API or an MCP server.

What is the difference between directory and custom connectors?

Directory connectors are submitted by developers and reviewed by Meta. Custom connectors are set up by Muse for one user, without review.

Can the same integration work in ChatGPT and Claude?

Yes. A Flow project serves the same tools as an MCP server for ChatGPT and Claude today.

Be ready when Muse comes asking.

One open-source TypeScript project. The same agent on WhatsApp, iMessage, Telegram, ChatGPT and more.