Connect another AI client

What an MCP client needs to work with quickS3, remote HTTP transport and OAuth sign-in, and the four steps to connect one and check its access.

Owner Admin Member AI user

Any MCP client that supports remote servers over Streamable HTTP, with OAuth sign-in, can connect to quickS3. The client finds the sign-in steps on its own, so there’s nothing to configure but the address.

Copy the server address from the AI agents page: https://quicks3.com/mcp.
Add it to your client as a remote (HTTP) MCP server.
Start the connection. The client opens quickS3 in your browser.
On the consent page, untick the roles the client doesn’t need, pick how long the access lasts, and select Authorize. See approve an AI client.
Ask the client to list your quickS3 connections to check it works.

Clients that don’t fit

Local-only clients (stdio servers only) can’t connect directly. Don’t work around it by copying access tokens into a script or config file.
Chat-only clients can list and browse, but can’t download or upload, because transfers need the client to run an HTTP request like curl. See how file transfers work.

Check the client is who it says

On the consent page, the client’s name is whatever the client reported, and anyone can pick any name. The “returns to” address is the part you can trust. If it doesn’t match the app you’re connecting, select Deny.