Quickstart: Meta Muse

Meta Muse has no connector form. You ask for the connection in a chat, Muse opens a Guardyx sign-in, and you pick the agent on a consent screen. There’s no API key, client ID, or config file to copy.

1. In the Guardyx portal, open My Agents and choose Connect new agent.
2. Under Which app will you chat with?, pick Meta Muse.
3. Choose the apps it should use and what it may do, then connect your accounts.
4. On the last step, copy the chat prompt. Leave the page open. Its status turns to Connected once Muse reaches Guardyx.

1. Send the prompt from the portal in a Muse chat. It reads like this:

   Connect Muse to the Guardyx MCP server at https://app.guardyx.ai/v1/mcp. Connect by signing in to Guardyx (OAuth), not with an API key.

   Keep the second sentence. If you only ask Muse to connect, it chooses an API key.

2. Muse opens a Guardyx sign-in window. Sign in.

3. On the consent screen, choose the agent you created and select Allow. Muse registered itself, so the screen also asks you to confirm that you started this connection. If someone sent you the link, cancel.

4. Back in the portal, the status changes to Connected.

Trust the Connected status, not Muse listing Guardyx’s tools. An older key-based connection also lists the tools.

1. Ask Muse for something that uses one of your connected apps, for example “What’s on my calendar today?”

   If Muse answers that no calendar is connected, it didn’t look in Guardyx. Your apps sit behind Guardyx’s search tool, so Muse doesn’t see them on its own. Name Guardyx in the request: “Use Guardyx to check what’s on my calendar today.”

2. Open Runs in Guardyx. The call is there, with its inputs, the policy decision, and the outcome.

3. Ask for something your policy holds for review. Muse waits while the request is in Approvals.

You can approve from your phone. For low- and medium-risk requests, the approval email has Approve and Deny buttons that open a confirm page without signing in. Each link works once and expires after 15 minutes. High- and critical-risk requests still need the portal or Slack. In the Slack mobile app, the approval message has Approve and Deny buttons.

Muse sees three Guardyx tools: guardyx_search_tools, guardyx_describe_tool, and guardyx_execute_tool. That is expected. Muse finds your toolbox’s tools by searching through them.

What you see	What to do
Muse never opens a Guardyx sign-in window	Send the prompt again. If the window still doesn’t open, use the API-key fallback.
Muse asks for an API key	Don’t create one. Ask Muse to connect by signing in to Guardyx.
Muse says it’s connected, but the portal still says it isn’t after a few minutes	Muse is still using a key from an earlier Custom MCP connection. Remove that Custom MCP agent in Guardyx, then send the prompt again.
“This agent has no bound tools”	Bind a toolbox to the agent on its page in Guardyx.
A tool shows not_connected	Connect that app’s account from the agent page, then retry.

If OAuth isn’t available, Muse can connect with an agent key instead.

1. In Connect new agent, pick Custom MCP (Another app that supports custom connections). From the last step you need only the API key (gx_live_…). You can ignore the JSON config.
2. Ask Muse: “Connect Muse to the Guardyx MCP server at https://app.guardyx.ai/v1/mcp.”
3. Muse sets up a custom connector that sends the key in an X-API-Key header.
4. Enter the key on Muse’s secure connector page. Never paste it into the chat. Muse stores the key and sends it only to the Guardyx host.
5. Ask Muse to list the server’s tools. It sees the three guardyx_* tools.

Every AI action passes through Guardyx. Each tool call Muse makes is checked against your policy, sensitive ones wait for your approval, and each request, decision, and outcome is recorded in a tamper-evident run trace.