Wasabi MCP is an OAuth-protected Model Context Protocol (MCP) server that lets an AI client operate your Wasabi account (S3, IAM/STS, WACM) without ever receiving your Wasabi access keys. The client gets a short-lived, scoped OAuth token; your Wasabi credentials stay encrypted on the server.
Wasabi’s MCP service is currently in beta and may be subject to changes, limitations, or occasional instability. Report any issues you encounter to Wasabi Support (support@wasabi.com).
Reference Architecture
.png)
Requirements
Active Wasabi storage account
Access and Secret Key Pair (see Wasabi's Access Keys Guide)
Access to a Cursor account
Configuring Cursor for Wasabi MCP
Log in to Cursor and click Settings.

Click Tools and MCPs.

Click Add Custom MCP.

Insert the code below.
{ "mcpServers": { "Wasabi S3": { "url": "https://mcp.wasabisys.dev/s3" }, "Wasabi IAM": { "url": "https://mcp.wasabisys.dev/iam" }, "Wasabi WACM": { "url": "https://mcp.wasabisys.dev/wacm" } } }Once the config is committed, the Tools & MCP page will list the newly added MCP servers.

Toggle each service and click Connect.

You will be directed to a webpage to log in. Provide the details below and click Sign in.
Wasabi account email address
Wasabi account password
MFA (optional)
.png)
Once signed in, click Add key to add your Wasabi access keys.

Provide the following details and click Save key.
Label—Name for the keys
Access key ID—Wasabi access key
Secret access key—Wasabi secret key

Once the keys are added, ensure S3 and IAM are highlighted in green (indicating they are enabled).

The configuration is complete. Click Return to AI editor.

Navigate to the Cursor MCP page. S3 and IAM should be active.

You can use natural language prompts to interact with Wasabi storage using Cursor.

If WACM is connected, you can use it to get information about the sub-accounts.
