Hosted MCP server/Cloud Storage

quickS3 MCP server

Hosted at quicks3.com·Streamable HTTP

quickS3 gives agents scoped access to S3-compatible storage, including S3, R2, B2, Wasabi, Spaces, and Azure. Through an HTTP MCP server, agents can list, upload, download, and share files without handing over access keys. The documented path is the Claude Code plugin: /plugin marketplace add QuickS3-com/skill, /plugin install quicks3@quicks3, then /mcp to authenticate. The plugin also ships a skill for narrow listing, link-based downloads, and non-overwriting uploads. File bytes travel directly between the client and the storage provider, so quickS3 sees metadata and tool requests but not file contents.

quicks3.com Streamable HTTP OAuth Server not checked yet Reviewed 2026-11-16
About

Where it fits

Developers and operations teams managing files across S3-compatible storage providers with scoped agent access.

  • Install the QuickS3 plugin and authenticate with /mcp.
  • List and download files through scoped links.
  • Upload without overwriting an existing object.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Claude Code plugin

Install the plugin, then run /plugin install quicks3@quicks3 and /mcp to authenticate. The plugin also ships a skill for narrow listing, link-based downloads, and non-overwriting uploads. The raw claude mcp add --transport http quicks3 https://quicks3.com/mcp command works as a manual endpoint alternative but skips the bundled skill.

  1. Add the marketplace

    In Claude Code, add the QuickS3 plugin marketplace.

    /plugin marketplace add QuickS3-com/skill
  2. Install the plugin

    Install the QuickS3 plugin, which includes the companion skill.

    /plugin install quicks3@quicks3
  3. Authenticate

    Run /mcp and complete the sign-in so the plugin can reach your storage.

    /mcp

Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.

Connection

Endpoint and configuration

Endpoint
https://quicks3.com/mcp
Host
quicks3.com · /mcp
Transport
Streamable HTTP
Authentication
OAuth
Server name
quicks3
Listing type
Community or directory listing

The installer uses the server name quicks3. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that quicks3 appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Install the QuickS3 plugin and authenticate with /mcp. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • The sign-in window closes without returning. Allow pop-ups and finish the provider login in the same browser.
  • The server connects but its tools are missing. Remove it, add it again, and approve the scopes the provider lists.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

quickS3 documentationhttps://quicks3.com/blog/connect-claude-code-to-s3-with-quicks3/GitHub repositoryhttps://github.com/QuickS3-com/skill