Connect Sides to OpenClaw
Give your personal assistant a careful first look at your Archive.
Before you start
Use an OpenClaw installation you control and a Sides account with an Archive. OpenClaw’s settings require administrator access. Choose an agent and conversation whose participants may see your Archive information; begin in a private conversation.
The connection uses Streamable HTTP and OAuth. Your installed client needs browser sign-in using a published client identity. Check the general connection requirements.
Add Sides and sign in
- Open OpenClaw’s Control UI and go to Settings → MCP. Under Configured servers, select Add server.
- Use the name sides-archive, choose Streamable HTTP, and enter:
https://app.sidesarchive.com/mcp
- Select Add server. In the scoped MCP configuration editor, find
sides-archiveunderservers. Use"auth": "oauth"with"transport": "streamable-http". Let the client discover Sides’ enabled permissions rather than pinning the old read-only scope. Keep its URL and transport, and leave other servers unchanged. Choose Save & Publish to apply the connection, then enable it. - Select Sign in on that server. Open the sign-in link from the dialog if the browser blocks the new tab.
- Complete Sides sign-in and consent, then return to Settings. Keep Sides enabled for the agent you intend to use.
Sign in with the Sides account that owns your Archive. Check the account and review the enabled read and write permissions offered together before approving consent. You don’t need a Sides client ID, client secret, callback registration, or copied token.
Use the Control UI on your OpenClaw installation’s own address for browser sign-in. If the installed version shows terminal instructions instead, follow OpenClaw’s MCP connection guide and OAuth instructions. If it asks for a manually registered client rather than opening Sides sign-in, check its published-identity support before continuing.
Check a first result
Start a fresh private conversation with the chosen agent and ask:
Use Sides to show me up to five Titles from my Archive, including the Copies I own. Don’t make any changes.
Check that it returns your records. Saved authentication does not replace this check. If the tools are missing, confirm that the server is enabled for that agent and refresh its connection. Keep the first test read-only.
Set an ongoing task
After the first result, specify a small selection, when to run, what output you want, and whether changes are allowed. Use your assistant’s scheduling controls and check its first completed run before relying on a schedule.
Hosted consent covers the enabled permission bundle upfront. Keep each task’s instructions narrow even when the connection permits writes. With the intake skill loaded, inferred metadata and artwork need component approval or explicit scoped direct intake; exact supplied edits can save directly. Deletions and existing-cover replacements retain their specific confirmations.
Load the matching optional task skill using your client’s supported loader; a connection alone does not load it. A standards-based package is not a claim of native OpenClaw acceptance.
Choose a review or research recipe. Sides does not schedule tasks or deliver Archive-change notifications.
Stop or reconnect
Pause the assistant’s Sides tasks first. In Settings → MCP, disable or remove the server. Follow OpenClaw’s OAuth sign-out instructions to clear the saved connection credentials. Reconnect with the same URL and complete sign-in when you want to use it again.
Stopping the task, removing the connection, removing a skill, and revoking provider permission are different actions. For help ending provider access, contact Sides support. Previously returned information cannot be taken back.
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.