MCP server
by tigrisdata
Tigris Storage offers S3-compatible object storage, manage aws s3 buckets, storage blobs, and binary large object storag
Connects AI agents to Tigris S3-compatible object storage for managing files, buckets, and generating shareable links. Enables file operations directly from AI chat interfaces.
Tigris Storage is an official MCP server published by tigrisdata that provides AI assistants with tools and capabilities via the Model Context Protocol. Tigris Storage offers S3-compatible object storage, manage aws s3 buckets, storage blobs, and binary large object storag It is categorized under cloud infrastructure, file systems.
You can install Tigris Storage in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Tigris Storage is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Read, analyze, and understand files in your project
Example
Summarize README, analyze code structure, find TODO comments across codebase
Navigate large codebases 5x faster, understand projects quickly
Create, move, rename, and organize files based on natural language instructions
Example
Organize downloads by file type, rename files following convention, batch process images
Save hours on manual file organization
Search files for patterns, extract data, find information across directories
Example
Find all config files with API keys, extract emails from documents, search logs for errors
Find information instantly instead of manual grep/find
Share your MCP server with the developer community
Tigris Storage has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
We evaluated Tigris Storage against two servers with overlapping tools; this profile had the clearer scope statement.
Strong directory entry: Tigris Storage surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Tigris Storage is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
According to our notes, Tigris Storage benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
We wired Tigris Storage into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Tigris Storage reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Tigris Storage has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Tigris Storage has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Tigris Storage reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
showing 1-10 of 73
[!IMPORTANT] Tigris has a hosted MCP server with OAuth support. Read more about it on mcp.storage.dev.
Tigris is a high-performance, S3-compatible object storage system designed for multi-cloud and AI workloads. We move your data all around the world based on where it's needed so that downloads are fast and the data is close to your users. You can store anything you want on Tigris (AI models, training data, database backups, request logs, social media uploads, or anything else) with no egress fees.
The Tigris MCP Server implements the MCP specification to create a seamless connection between AI agents and Tigris key features like bucket and object management.
The Tigris MCP server provides your agents context to your Tigris buckets and objects. That allows you to use Tigris in your AI editor workflows.
Here are some example prompts you can try:
my-bucketmy-bucketmy-bucket/Users/ME/tigris-mcp-server/myfile.txt to my-buckettest in my-buckettest.txt with content Hello World in my-buckettest.txtmyfile.txt from my-bucketCheckout our blog post about Vibe coding with Tigris MCP Server and more tips on sharing files using Tigris MCP Server
As Tigris supports the S3 API, you can use the wide range of available S3 tools, libraries, and extensions. You can get AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY from webconsole by following these the steps. Please refer to our Tigris Data documentation for detailed overview.
To get started:
AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY to a safe place like your password manager. These will not be shown again.Tigris MCP server can be used both with npx and docker. We recommend running with docker as it provides better sandboxing.
We support installing the Tigris MCP server two ways:
We suggest installing and using the MCP server with Docker as it provides much better sandboxing than NPX.
docker requires the Docker Engine to be installed. If you don't have it installed, follow the instructions here.npx requires Node.js to be installed. If you don't have it installed, follow the instructions here.Click one of these buttons to install the Tigris MCP Server for VS Code or VS Code Insiders.
You can install the Tigris MCP server in Claude Desktop and Cursor by running our install script:
npx -y @tigrisdata/tigris-mcp-server init
If you don't want to use our automatic install script, you can manually install the Tigris MCP server by adding one of these blocks to your MCP client's configuration.
For Claude Desktop, edit one of the following files:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonTo open the right file in Cursor:
Then add one of the following blocks to the end of your configuration:
{
"mcpServers": {
"tigris-mcp-server": {
"command": "npx",
"args": ["-y", "@tigrisdata/tigris-mcp-server", "run"],
"env": {
"AWS_ACCESS_KEY_ID": "YOUR_AWS_ACCESS_KEY_ID",
"AWS_SECRET_ACCESS_KEY": "YOUR_AWS_SECRET_ACCESS_KEY",
"AWS_ENDPOINT_URL_S3": "https://fly.storage.tigris.dev"
}
}
}
}
Please note that the server will only allow operations within `/User/CURRENT_USER/tigris-mcp-server. This allows for a secure sandboxing environment.
{
"mcpServers": {
"tigris-mcp-server": {
"command": "docker",
"args": [
"-e",
"AWS_ACCESS_KEY_ID",
"-e",
"AWS_SECRET_ACCESS_KEY",
"-e",
"AWS_ENDPOINT_URL_S3",
"-i",
"--rm",
"--mount",
"type=bind,src=/Users/CURRENT_USER/tigris-mcp-server,dst=/Users/CURRENT_USER/tigris-mcp-server",
"quay.io/tigrisdata/tigris-mcp-server:latest"
],
"env": {
"AWS_ACCESS_KEY_ID": "YOUR_AWS_ACCESS_KEY_ID",
"AWS_SECRET_ACCESS_KEY": "YOUR_AWS_SECRET_ACCESS_KEY",
"AWS_ENDPOINT_URL_S3": "https://fly.storage.tigris.dev"
}
}
}
}
Alternatively, you can use your existing AWS Profiles if you have AWS CLI installed and have your AWS credential configured. You can use the following configuration.
{
"mcpServers": {
"tigris-mcp-server": {
"command": "npx",
"args": ["-y", "@tigrisdata/tigris-mcp-server", "run"],
"env": {
"USE_AWS_PROFILES": "true",
"AWS_PROFILE": "default",
"AWS_ENDPOINT_URL_S3": "https://fly.storage.tigris.dev"
}
}
}
}
or via docker
{
"mcpServers": {
"tigris-mcp-server": {
"command": "docker",
"args": [
"run",
"-e",
"USE_AWS_PROFILES",
"-e",
"AWS_PROFILE",
"-e",
"AWS_ENDPOINT_URL_S3",
"-i",
"--rm",
"--mount",
"type=bind,src=/Users/CURRENT_USER/tigris-mcp-server,dst=/Users/CURRENT_USER/tigris-mcp-server",
"quay.io/tigrisdata/tigris-mcp-server:latest"
],
"env": {
"USE_AWS_PROFILES": "true",
"AWS_PROFILE": "default",
"AWS_ENDPOINT_URL_S3": "https://fly.storage.tigris.dev"
}
}
}
}
For development, refer to the CONTRIBUTING.md file.
Generate boilerplate files, apply templates, create project structures
Example
Create React component with tests and styles, generate OpenAPI spec, scaffold new project
Eliminate repetitive file creation work
Prerequisites
Time Estimate
10-20 minutes including configuration
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
MCP server provides file I/O operations (read, write, search, metadata) as tools Claude can invoke with natural language instructions.
Protocols
Compatibility
✓ Use when
Use for code analysis, file organization, content search, template generation, and automating repetitive file operations. Best for local development workflows.
✗ Avoid when
Avoid for system-critical files, sensitive credentials, production environments, or when file integrity is paramount. Don't use on files you can't afford to lose.