CellCog for Muse

Your Muse now has super-agents.

For Muse

The studio your Muse sends work to

Muse runs your life. It reads, plans, books and pays. When you ask it for a video, a deck, a spreadsheet, an app or a real piece of research, it hands the job to CellCog and brings the finished files back into your Muse.

How to connect

Facts on this page verified September 19, 2026.

How it works

Muse briefs. CellCog makes. Muse delivers.

1. Ask Muse"Turn my launch notes into a 60-second video and a one-page PDF." Muse knows CellCog does this and hands over the brief and the files.
2. Connect onceThe first time, Muse asks you to connect CellCog: sign in or sign up, approve, done. Sentinel asks before CellCog is used, on your terms (once, for this task, or always).
3. Get the work backMinutes later the finished files are in your Muse: the video, the PDF, the deck, the spreadsheet, the app link, the report with sources. Muse saves them, sends them, posts them.
What comes back

Finished work, as files Muse can use

Videoads, reels, explainers and films with dialogue, music and sound
Imagesad creative, product photos, logos, infographics, edits
DocumentsPDFs, reports, slide decks, one-pagers
Spreadsheetsmodels with real formulas, analysis, charts
Apps and dashboardsworking web pages and interactive dashboards, hosted
Researchdeep research with sources (ranked #1 on DeepResearch Bench in July 2026)
Audiovoiceovers, music, sound effects, podcasts
Code and data workprototypes, data analysis, automation scripts

Every job is done by an agent that writes the script or copy, makes the asset and checks its own result before it answers. Benchmark receipts: cellcog.ai/benchmarks.

Connect

Three ways in, two of them today

Custom connector (today)Say "connect CellCog" in Muse. Muse builds the connector itself from the CellCog API, following the skill below. You create an API key at cellcog.ai and hand it to Muse once.
Muse Code (today)Muse Code speaks MCP. Add https://cellcog.ai/mcp as a streamable HTTP server; sign in once with your CellCog account (OAuth). Seven tools: create a job, send a message, upload files, check status, get the result, list chats, account.
Muse connector directorycoming: CellCog in the Muse connector directory. When it is listed, connecting is one tap inside Muse, no key to hand over.

Muse Code configuration (settings file):

{
  "mcp_servers": {
    "cellcog": {
      "transport": "streamable_http",
      "url": "https://cellcog.ai/mcp",
      "enabled": true
    }
  }
}
For Muse to read

The CellCog skill

This is the connector, written the way Meta writes its own: a skill that tells Muse when to hand work to CellCog and how. A Muse reading this page can build the custom connector from it; the markdown version is at cellcog.ai/muse/index.md.

SKILL: CellCog for Muse
Use CellCog when the person asks for finished work that is a file: a video, images,
a PDF or deck, a spreadsheet, a web app or dashboard, or research with sources.
Muse briefs. CellCog makes. Muse delivers.

Connect once: the person creates an API key at https://cellcog.ai/profile?tab=api-keys
and hands it to you as CELLCOG_API_KEY. Never ask for their password.

Run (Python, in your own environment):
  pip install cellcog
  from cellcog import CellCogClient
  client = CellCogClient(agent_provider="muse")
  result = client.create_chat(
      prompt="Turn these notes into a 60-second video and a one-page PDF ...",
      chat_mode="agent",        # agent | creative | team
      timeout=3600,
  )
  # finished files land in ~/.cellcog/chats/<chat_id>/ (or a path you name)

Brief well: name every deliverable and its format. Attach inputs by wrapping each
absolute path in a SHOW_FILE tag inside the prompt (the SDK README shows the exact
form); a bare path is text, not a file. One request may ask for several outputs.

Long jobs: create_chat(..., delivery="send_only") returns at once; poll
client.get_status(chat_id); collect with client.wait_for_completion(chat_id).

Out of credits: the call fails with a message that carries the top-up link. Show it
to the person, then retry after they add credits.

Do not: publish to the person's accounts (that is your job, after the work is back),
pick a model or preset (CellCog chooses), or send files the person did not hand you.
Questions

Frequently asked

Does CellCog act in the world from Muse?

No. CellCog takes a brief and returns finished files. Sending the email, posting the video, paying for something: those stay with Muse, under Sentinel, exactly where Meta put them.

What does it cost?

CellCog is free to try, no credit card needed. After that you pay for the work, not the connection; the cost depends purely on how much work you assign. Current plans are at cellcog.ai/pricing. Muse tokens and CellCog credits are separate.

Who sees my files?

Only your CellCog account. Files you hand over are used for that job; results come back as links valid for 30 days and are downloaded into your Muse. You can revoke the connection any time from your CellCog profile.

Is this an official Meta connector?

Not yet. Today it works as a custom connector Muse builds from our API, and through MCP in Muse Code. We have submitted CellCog to the Muse connector directory; this page says so the day it is listed.

Can Muse hire an AI employee through CellCog?

Not from Muse in this version. CellCog also runs AI employees who own a role over time (a receptionist, an SDR, a researcher); that is the next step, and you can hire one at cellcog.ai/ai-employees today.

Give your Muse a studio.

Free to try, no credit card needed. Create a CellCog account, make an API key, and tell Muse to connect CellCog. The first job can start in the same minute.

Muse is a trademark of Meta Platforms, Inc. CellCog is an independent product.