Quick Start: Agent Central + Muse

Before you start

• An Agent Central account with Amazon connected
• An API key or signed Connector URL from the dashboard Keys tab
• Access to Muse with Custom Connectors and secure credential entry available

You do not need a reviewed catalog listing to create a private Custom Connector. Meta does not review custom connectors.

1. Choose your connection method

With an API key, connect through the REST API. With a signed Connector URL, connect through the MCP server. These are different credential formats; neither can be entered in the other’s credential field. Use the method for the credential you have.

Both use the account, marketplace and permissions attached to the credential.

2A. Connect with an API key

Create a Custom Connector named Agent Central using its REST API.
API base URL: https://mcp.agentcentral.to/v1
API documentation: https://agentcentral.to/docs/rest-api
Authentication: send my API key in an Authorization header with the Bearer prefix.

Ask me for the API key through your secure credentials form, not in chat.
Keep it in your Secure Credentials Store, never in chat, files or screenshots.
If secure entry is not available, stop.

Save the connection for future conversations. Verify the saved connection with
a read. Only report success if verification succeeds. Then run the Agent Central
account data tour. Confirm the account, marketplace, available data areas,
permissions and latest source dates. Do not change anything.

Enter your API key only in Muse’s secure credentials form. Muse sends it to https://mcp.agentcentral.to/v1 in an Authorization header with the Bearer prefix. If the form requests the complete header value instead of the key alone, enter Bearer, one space, then the full key.

Ask Muse to verify the saved connection before running the data tour.

2B. Connect with a signed MCP Connector URL

A signed Connector URL has this structure (the placeholder is not a working credential): https://mcp.agentcentral.to/mcp/connect/<token>.

Create a Custom Connector named Agent Central MCP.
Transport: remote Streamable HTTP
Server URL format: https://mcp.agentcentral.to/mcp/connect/<token>
Authentication: the signed token in the URL path, not a Bearer API key.

Open a secure credentials form for only the token after /mcp/connect/.
Do not ask for the full Connector URL in a token field. Do not ask me to paste
any credential into chat, files or screenshots. Keep the token in your
Secure Credentials Store. If secure entry is not available, stop.

Use that secure token in the URL path when connecting. Do not try to read a
stored full URL back from the vault to extract its token. Save the connection
for future conversations, then verify the stored connection with a read.
Only report success if verification succeeds. Then run the Agent Central
account data tour. Confirm the account, marketplace, available data areas,
permissions and latest source dates. Do not change anything.

1. Locate the signed Connector URL in your Agent Central dashboard.
2. Copy only the characters after /mcp/connect/ into Muse’s secure token form. Do not include the full URL or an API key.
3. Ask Muse to verify the saved connection. Do not treat the connection as working just because the form says it was saved.

The token belongs in the server URL path, not an Authorization header. Muse must insert the secure token directly into that path. It cannot retrieve a stored full URL and split it later.

3. Run the data tour

Once the saved connection is verified, ask Muse to run the account data tour:

Run the Agent Central account data tour. Start by confirming the connected
account, marketplace, permissions and latest source dates. Summarize the
available sales, advertising and inventory data. Flag missing or stale data.
Do not change anything.

The tour shows what data is available and how current it is. Confirm the account and marketplace are the ones you intended. Missing history is not zero activity: a new connection needs its initial sync, and some reports arrive later than others.

Use the saved connection or switch accounts

In a later conversation, ask Muse to use the saved Agent Central connection and confirm the account again. Do not re-send credentials in chat.

To change accounts, ask Muse to reconnect through its secure form, then verify the new account and marketplace. Replacing a saved credential may replace access to the previous account; it does not revoke the old credential in Agent Central. Existing charts or dashboards may still show the previous account’s data until you rebuild them.

Troubleshooting

Muse asks for a credential in chat or cannot offer secure entry

Do not send it. Keep credentials in Muse’s Secure Credentials Store. Do not continue unless Muse offers secure entry. If you exposed a credential, revoke the associated key in Agent Central and replace it.

Invalid API key

Check that the secure form received an API key, not a signed Connector URL or its token. Check for a truncated copy, a revoked key or a duplicated Bearer prefix.

Invalid connector token

If Muse’s form expects a token, enter only the part after /mcp/connect/ through a fresh secure form. A full URL in that field is not a token. Do not ask Muse to retrieve the stored full URL and parse it. If verification still fails, stop rather than expose the URL or token in chat.

The account is wrong or data is missing

Check which credential Muse is using. Review the connected account, marketplace and available data areas in the dashboard. Ask Muse for source dates and data gaps before relying on the answer.

Further reading

• How Agent Central works
• REST API documentation
• Meta: Custom Connectors and the Secure Credentials Store
• Meta: Muse permissions and approvals