NetworkOS in Meta Muse

Muse is Meta's personal agent: it runs on its own cloud computer, works across the apps you connect, and keeps going after you close the app. Once NetworkOS is connected, you can ask Muse about anyone you know, search your contacts in plain English, log notes and tags, see introductions in flight, find the people you are overdue to catch up with, and draft and send warm introductions from your own Gmail. It is the same connector that works in Claude and ChatGPT, answering in text inside your Muse conversation.

Claude and ChatGPT open a NetworkOS sign-in in your browser. Muse builds custom connectors itself, on its own machine, and its setup flow takes either no authentication or a bearer token. So NetworkOS gives you a token: generate it under Settings, AI connectors, Meta Muse, pick what it may do, and paste it into Muse's credential prompt. NetworkOS stores only a hash of it, one token is live at a time, it expires after a year, and you can revoke it from the same place. Muse is available in the US to adults, on iOS, Android, the web and Mac, free for up to 100M tokens a week. Custom connectors are built by Muse itself and are not reviewed by Meta.

1. 1

   Generate a personal access token

   In NetworkOS, open Settings, then AI connectors, pick Meta Muse, choose read-only or read and write, and click Generate token. Copy it now: it is shown once. If you lose it, generate a new one and the old one stops working.

2. 2

   Ask Muse to build the connector

   Open Muse and send it this message: Build a custom integration to NetworkOS. Its MCP server is at https://www.thenetworkos.com/api/mcp (remote, streamable HTTP, bearer token auth). I want to search my network, look up how I know someone, draft double opt-in introductions from my own inbox, and see who I am overdue to catch up with. Test it with one search, then save it as a skill called NetworkOS.

3. 3

   Answer Muse's two questions

   Muse asks whether the server is remote or local, and how it authenticates. Answer remote over HTTP and bearer token.

4. 4

   Paste the token into Muse's credential prompt

   When Muse asks for the token it opens a secure entry field. Paste the token there, not into the chat: what you type there goes to Muse's credential store, which the agent cannot read back.

5. 5

   Test it and save it as a skill

   Muse calls one tool and shows you the result. Confirm it saved the connector as a skill named NetworkOS, then try it from a fresh conversation: Who do I know at Stripe?

6. 6

   Set the approval policy

   In Muse, open Settings, then Connectors. Keep NetworkOS read-only, or require approval for every action, so Muse asks before it sends an introduction from your inbox.

The message to paste, in full:

Build a custom integration to NetworkOS. Its MCP server is at https://www.thenetworkos.com/api/mcp (remote, streamable HTTP, bearer token auth). I want to search my network, look up how I know someone, draft double opt-in introductions from my own inbox, and see who I am overdue to catch up with. Test it with one search, then save it as a skill called NetworkOS.

Each example below is something you can say to Muse once the connector is saved as a skill. Muse answers in text and, where a step changes something, asks you before it goes ahead.

The connector exposes read tools for finding and reviewing, such as searching contacts and companies, finding intro opportunities, network insights, and listing notes, tags, introductions and catch-ups, and write tools for acting: creating and updating contacts, adding notes and tags, drafting and sending introductions and catch-ups, and recording outcomes. A read-only token only exposes the first group.

Read tools: search_contacts, query_contacts, search_companies, list_companies, find_intro_opportunities, get_network_insights, get_contact_detail, list_contact_notes, list_tags, list_introductions, get_introduction, list_catch_ups, get_catch_up.

Write tools: create_contact, update_contact, archive_contact, add_contact_note, update_contact_note, delete_contact_note, create_tag, add_contact_tag, remove_contact_tag, create_introduction_draft, regenerate_introduction_drafts, update_introduction_draft, send_introduction_email, mark_introduction_outcome, draft_catch_up, update_catch_up, send_catch_up.

You control this in two places, and either one is enough. In NetworkOS, generate a read-only token and Muse cannot change anything, whatever it is asked. In Muse, open Settings, Connectors and set NetworkOS to require approval for every action, and Muse will show you each send or edit before it happens. By default Muse already asks before sending an email.

Muse says the server returned 401 or that the token was rejected. The token was revoked, expired, or a new one was generated (which retires the old one). Generate a new token in NetworkOS, then tell Muse to update the NetworkOS credential and paste it into the credential prompt.

Muse asks you to sign in with OAuth, or opens a browser to NetworkOS. Tell it the server uses a bearer token, not OAuth. The prompt above says so, but Muse sometimes reads the server's OAuth metadata first.

Muse wants to build from an API document instead. Give it the MCP address again, https://www.thenetworkos.com/api/mcp, and say it is an MCP server over streamable HTTP. There is no separate REST API to use.

Muse forgets the connector in a new chat. Ask it whether the NetworkOS skill is saved; if not, repeat the setup message and finish with “save it as a skill.”

Muse is not available to you. At launch Muse is offered in the US to adults, on iOS, Android, the web and Mac. The connector itself has no such limit, so the same endpoint works in Claude and ChatGPT today.

Anything else, email support@thenetworkos.com with what Muse said; we will check the connector logs on our end.

Muse runs custom connectors on its own virtual machine, and Meta does not review them; treat the token like a password and read Meta's connector article for how Muse handles what it retrieves. On our side the connector respects the same boundaries as the app: NetworkOS sends introductions from your own Gmail, opens full message content only where a feature needs it, and returns to Muse only what a tool call asks for. See Privacy & your data for details, or revoke the token any time from Settings.