Connect another AI assistant

Use one Sides address with an assistant that supports remote MCP sign-in.

What your assistant needs

Look for Connectors, Integrations, or MCP servers in your assistant’s settings. It needs to support remote MCP over Streamable HTTP and browser-based OAuth sign-in with a published client identity, sometimes called CIMD.

MCP support alone does not mean every connection method is available. A local-command-only connection or a form that requires a manually issued API key is not the connection to choose for Sides.

Prefer the specific instructions for ChatGPT, Claude, or OpenClaw when using one of those assistants.

Add a remote connection

  1. Choose Add connector or Add MCP server. Give the connection the name Sides.
  2. Choose a remote URL connection with Streamable HTTP as the transport. Enter:
https://app.sidesarchive.com/mcp
  1. Choose OAuth or browser sign-in. Let the assistant discover the sign-in settings. If it asks how to identify itself, choose its published identity or CIMD option.
  2. Save or connect, then follow the browser sign-in. Review the offered read and write permissions for the Sides account that owns your Archive before approving consent.
  3. Return to the assistant, enable Sides for the conversation or agent, and refresh its available tools.

You do not need a local server, an API key, a Sides-issued client ID, an application registration, or a copied token. Keep your password and browser-session details out of conversations.

If the assistant cannot offer browser sign-in or a published client identity, use its maintained connection guide or contact support with its name and version. Don’t substitute an unrelated registration, turn authentication off, or add a bearer token.

Check the connection with a small question

Use Sides to show me up to five Titles from my Archive, including the Copies I own. Don’t make any changes.

Check that the records are yours before sharing more information or allowing an edit. A saved server entry alone is not the result: your assistant must actually read the records. If no tools appear, refresh the connection or open a fresh conversation.

No skill is needed for this check. For repeated work, give your assistant a bounded ongoing task.

Choose when to allow changes

Sides requests its enabled read and write permissions together during hosted sign-in, including deletion, original artwork access and full Archive export. Review that consent before agreeing. Existing partial grants remain limited; connecting or installing a skill never silently expands them.

Your instructions and your assistant’s controls determine what to do with that access. With the optional intake skill loaded, researched metadata and artwork are proposed together before saving. You may approve metadata, artwork or both, or explicitly allow direct intake for either component and a stated scope. Exact corrections you supply can save directly. Deletion and replacing an existing cover retain their specific confirmation requirements.

If tools are missing, refresh discovery and start a fresh conversation. If the grant is incomplete, deliberately reconnect and review the current consent. Avoid repeated permission-upgrade attempts. A skill cannot grant access. More about permissions.

The remote connector supplies tools, not the Sides task procedures. Choose the plain skills or combined standards-based plugin only through a format your client supports. Confirm the intended skill actually loads; importing a package and connecting the account are separate steps.

Disconnect or reconnect

Stop tasks using Sides, then disable or remove the Sides connection in your assistant’s settings. Follow the assistant’s own instructions for signing out of that saved connection. Reconnect with the same URL and hosted sign-in when you want access again.

Removing a local connection or skill and revoking permission at the sign-in provider are separate actions. For help ending provider access, contact Sides support. Information already returned cannot be taken back by disconnecting.

If a change was interrupted, keep the conversation. Ask your assistant to recover the same request with its original details and retry key, then read the current record before trying a new change.

MCP authorization standard · More help with your Archive

Sides is in beta.

Start building your Archive now. Sign up before January 1, 2027 (Pacific time), and your 14-day trial clock won’t start until January 1.

You can use Sides through January 14, 2027 (Pacific time), with up to 50 Titles and 5 Maestro assists for the whole trial.

Use the extra time to explore Sides with your own recordings and let us know what could work better.

Start free trial