> ## Documentation Index
> Fetch the complete documentation index at: https://docs.agentvault.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Meta Muse

> Add Agent Vault to Meta Muse as a custom connector and sign in, in about 2 minutes.

Connect Meta Muse to Agent Vault so it can check out and sign in for you, using
only mock tokens. It takes about 2 minutes, and you set it up by asking Muse in
the chat.

<Frame caption="Copy the line for Meta Muse from your dashboard, paste it into Muse, and sign in.">
  <video controls muted playsInline preload="metadata" className="w-full" poster="/images/agents/meta-muse-poster.webp" src="https://mintcdn.com/self-labs/VeDWRFlNWGO5jQN6/videos/agents/meta-muse.mp4?fit=max&auto=format&n=VeDWRFlNWGO5jQN6&q=85&s=2b1767457b896864b2054eb095d90c91" aria-label="The dashboard's Connect another agent panel with Meta Muse picked, and its line being copied." data-path="videos/agents/meta-muse.mp4" />
</Frame>

## Before you start

* An Agent Vault account, with a card if your agent will check out. New here?
  The [Quickstart](/get-started/quickstart) sets one up in about 5 minutes.
* Meta Muse, with custom connectors available on your account.

## Connect Meta Muse

<Tabs>
  <Tab title="Paste one line (recommended)">
    <Steps>
      <Step title="Paste this into Muse">
        ```text theme={null}
        Read https://mcp.agentvault.io/skill.md and follow it to connect Agent Vault. Sign-in uses dynamic client registration, so no client ID or secret is needed.
        ```

        Muse reads the connect skill and creates a custom connector called
        **Agent Vault**. The second sentence matters: without it, Muse may ask you to
        create an app and type in a client ID and secret. You don't need either.
      </Step>

      <Step title="Sign in">
        Muse shows a sign-in link for the connector. Open it and sign in on the
        Agent Vault sign-in page, with your Agent Vault account.
      </Step>
    </Steps>
  </Tab>

  <Tab title="Set it up by hand">
    <Steps>
      <Step title="Ask Muse to add the connector">
        Send Muse this message:

        ```text theme={null}
        Create a custom connector called Agent Vault for the MCP server at `https://mcp.agentvault.io/mcp`. It uses MCP OAuth with dynamic client registration: the connector registers itself, so don't ask the user for a client ID, client secret or redirect URI, and don't ask them to create an app anywhere. The protected resource metadata is at `https://mcp.agentvault.io/.well-known/oauth-protected-resource`, and it links to the authorization server's metadata, which has the `registration_endpoint`.
        ```
      </Step>

      <Step title="Sign in">
        Muse shows a sign-in link for the connector. Open it and sign in on the
        Agent Vault sign-in page, with your Agent Vault account.
      </Step>
    </Steps>
  </Tab>
</Tabs>

## Choose what it may use

A new connection starts with nothing granted, so your agent can't use a card or
a login yet. Until you choose, its first tool call answers:

```text theme={null}
Choose what this app may use in Agent Vault before it can act: open the connection's page in the dashboard.
```

The connection itself appears in the dashboard only once your agent makes its
first tool call, so make that call first.

<Steps>
  <Step title="Make a first call">
    Ask your agent to call `get_token_catalog`. It answers with the message above,
    and the call creates the connection.
  </Step>

  <Step title="Open Connected apps">
    In the dashboard sidebar, under **Vault**, click **Connected apps**. The new
    connection's row shows **Choose what it may use**.
  </Step>

  <Step title="Pick its cards and logins">
    Click **Choose access**. Under **Cards** and **Logins**, pick **All**, or keep
    **Only selected** and tick the ones this agent may use.
  </Step>

  <Step title="Check the choices, then click Save access">
    Your first connection's dialog opens with nothing ticked. After that, a new
    connection's dialog opens with the choices of the connection you used most
    recently, so saving it unchanged grants the same cards and logins, and the same
    three switches: **Let this app create and change its own logins**, **Ask me
    before every purchase from this app** and **Fill a test card instead of my
    card**. Check all of them for this agent before you click **Save access**.
  </Step>
</Steps>

You can change or revoke the connection on the same page at any time. See
[Connected apps](/dashboard/api-keys#connected-apps).

## Check it works

Ask Muse to call the Agent Vault tool `get_token_catalog`. It answers with the
mock tokens for the cards and logins you allowed, such as
`av_card_1_number_u7x2k`. Your real card number never reaches the chat.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Muse asks for a client ID, client secret or redirect URI">
    You don't need any of them: the connector registers itself. Tell Muse that
    sign-in uses dynamic client registration, or send the message from
    **Set it up by hand**, which says so in full.
  </Accordion>

  <Accordion title="The first tool call says to choose what this app may use">
    The connection has nothing granted yet. Follow
    [Choose what it may use](#choose-what-it-may-use), then ask again.
  </Accordion>
</AccordionGroup>

## Next

<CardGroup cols={2}>
  <Card title="Your first checkout" icon="cart-shopping" href="/guides/first-checkout">
    Have Muse buy something, start to finish.
  </Card>

  <Card title="All agents" icon="plug" href="/agents/overview">
    Connect another agent to the same vault.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.