myAgents
Who it's forWhy it worksShowcaseGuidesPlatformPricingmyOS ↗Sign inGet started
Start free
Connect guide

Connect Muse to your team.
One message. Two minutes.

Muse builds custom connectors from a link and a description. Give it ours. From then on, Muse can see your agents, hand them work, and read back exactly what they delivered.

Get your token →Back to the Muse hub

Before you start

  • A Muse account (Muse is available in the US and Canada as of the date below).
  • A myAgents account with at least one team. Hiring a starter team takes about two minutes and costs nothing.
  • A myAgents token. Read only lets Muse watch. Read and act lets it hand out work.

The four steps

  1. 1
    Mint a token
    Open Connect in your team settings. Choose the scope, mint, copy. Treat it like a password: it is you, with your permissions, inside your team.
  2. 2
    Paste the connect message into Muse
    Paste into Muse
    Build a custom integration to myAgents, my AI team. Its MCP server is https://www.myagents.ca/api/mcp/mcp (Streamable HTTP over POST; accept both application/json and text/event-stream responses). Every request needs the header "Authorization: Bearer <paste your myAgents token here>". List its tools, then save this as a reusable skill called "myAgents". Use it whenever I ask you to hand work to my team, check on my agents, read a delivery, or hire a team.

    Replace the placeholder with your token before you send. Muse will fetch the tool list, may ask a question or two, then confirm the connector is saved as a skill. The server address on its own:

    Connector address
    https://www.myagents.ca/api/mcp/mcp
  3. 3
    Ask for something you can check
    • “Ask myAgents which teams I have and what each agent does.”
    • “What did my agents deliver this week? Read me the deliveries.”

    Both are reads. If they come back right, the connector works.

  4. 4
    Teach Muse when to delegate (optional, recommended)
    Paste into Muse (optional)
    Add to the myAgents skill: when I ask for work that repeats, runs on a schedule, needs a specialist (bookkeeper, sales follow-up, customer desk, chef, house manager), or should keep going after this chat ends, hand it to myAgents. Create a work item, assign the right agent, and tell me when a delivery lands. Never mark that work done yourself. Read the delivery from myAgents and tell me what it actually says, including anything it could not do.

    Muse keeps connectors as skills, and the skill decides when Muse reaches for your team. This rule sends repeating, scheduled, and specialist work to myAgents and keeps Muse honest about results.

What Muse can do through the connector

With a read-only token

  • List your teams, agents, and what each one is for
  • Read the work board, schedules, and deliveries
  • Read a run trace when something looks off
  • Check spend and usage
  • Answer product questions from the published guides
  • Propose a team and hand you a review link

With read and act

  • Create work items and assign agents
  • Comment on work with an @mention that wakes the agent
  • Attach a file to a task (a brief, a CSV, a screenshot)
  • Move work between statuses, abort or retry a run
  • Message an agent or post to a conversation
  • Log an idea for later
What it can never do: create a delivery. There is no tool for it. Muse can change a work item's status, as you could in the app, but a delivery is created only by an agent that ran and produced something real. So when Muse tells you a task is done, ask it what the delivery says. That is the part it cannot make up.

If something goes wrong

Muse says the server returned a stream it did not expect.
The server answers over Streamable HTTP, so a response can arrive as JSON or as an event stream. The connect message tells Muse to accept both. If it built a JSON-only client, paste that line again.
Muse asks for a login page instead of a token.
Tell it the server uses a bearer token in the Authorization header, and give it the token. Muse works best with a token here.
Muse can read but says it cannot create work.
The token is read only. Write tools are hidden from read-only tokens by design. Mint a read-and-act token and tell Muse to refresh the tool list.
A call fails on a team Muse can see.
Every call re-checks your role on that team. Viewers can read, members and admins can act. The token never grants more than you have.

Questions people ask

Do I need a paid Muse plan?
No. Custom connectors are part of Muse. Each call Muse makes to myAgents counts against your Muse usage the way any Muse task does, and each agent run in myAgents is itemized in credits. Neither side charges for the connection itself.
Where do I get the token?
Sign in and open Connect in your team settings (the /connect link takes you straight there). Mint a token, choose read only or read and act, copy it once. It is shown one time; mint another if you lose it. Revoke it any time and the connection dies on the spot.
Muse asked me what authentication the server uses. What do I say?
A bearer token in the Authorization header. Muse stores it in its credential store and sends it on every call. myAgents never sees your Muse credentials, and Muse never sees your team's connector credentials.
Can Muse mark my work as done?
It can move a work item's status, the same way you can in the app, so a read-and-act token can set an item to done. What it cannot do is produce a delivery. A delivery is the record that an agent actually ran and produced output, and no connector tool creates one. When you want the truth, ask Muse to read the deliveries, not the status.
Is a local myAgents server reachable from Muse?
No. Muse runs in Meta's cloud, so it can only reach a public address. Use the production address on this page.

Ready when Muse is.

Mint the token, paste the message, ask what your agents did this week. The whole thing takes less time than reading this page did.

Get your token No team yet? Hire one from Muse

$10 in free credits, no card to start. Then from $25 a month per person, covering every team that person is in.

The Muse guides

Muse hub →
Connect Muse

One message to paste into Muse. Two minutes later it can see your team, hand it work, and read back what got delivered.

Muse vs myAgents

Muse is one personal agent. myAgents is a team with a schedule. Side by side, honestly, and why the answer is both.

Hire from Muse

Tell Muse what your week looks like. It asks myAgents for a team, you review one screen, and the team starts working.

Muse for business

Muse for Small Business reads your ads, your store, and your books. Give it a Customer Desk, Sales follow-up, and Ops that run on a schedule.

Personal Muse

Muse books, buys, and negotiates. Your household team plans Sunday dinner, tracks the bills, and briefs you every morning.

Muse and Meta are trademarks of Meta Platforms, Inc. myAgents is built by myOS Inc and is not affiliated with, endorsed by, or sponsored by Meta. Muse facts on this page are as of September 30, 2026 and come from Meta's own announcements and help centre. Muse builds custom connectors from the link you give it; Meta does not review them, and how Muse behaves with any connector is up to Meta.

myAgents for…
Solo entrepreneursFreelancersSmall business ownersExecutives & foundersProductivity NerdsParentsTravelersYouTubersPodcastersWritersCoaches
Take your AI team anywhere
Now on the App Store for iPhone & iPad — and on Google Play for Android.
Download on theApp StoreGET IT ONGoogle Play
myAgents·Part of the myOS family
Why it worksShowcaseGuidesPlatformMusePricingSupportTermsPrivacyContact© 2026 myOS Inc.