Tigris' MCP Server Goes Global
A digital illustration of a cartoon bengal tiger high-fiveing a robot on a backdrop of the astral plane with floating mountains.
We’ve made it easier to integrate Tigris into your AI workflows by removing the most complicated part of getting started with the MCP server: installing it. This lets you integrate Tigris into your ChatGPT, Claude, and agentic coding workflows in a snap!
Here's how you get started:
- ChatGPT (web)
- Claude Desktop
- Claude Code
- Cursor
- OpenAI Codex
- VS Code
- Open ChatGPT Settings and click "Create" on top right corner of Settings modal
- In the Name field, enter "Tigris"
- In the MCP Server URL field, enter "https://mcp.storage.dev/mcp"
- In the Authentication field, select "OAuth"
- Click "Create"
- Go to Settings > Connectors - Click on Add custom connector button - In
the Name field, enter "Tigris" - In the Remote MCP server URL field,
enter
https://mcp.storage.dev/mcp- Click "Add" button - Once the connector is added, Click on "Connect" button and complete the authentication flow.
Run this command:
claude mcp add --scope user --transport http tigris https://mcp.storage.dev/mcp
Then run claude use the /mcp command to authenticate.
Run this command:
codex mcp add --url https://mcp.storage.dev/mcp tigris
Then run codex and use the /mcp command to authenticate.
Click this button:
Or do the following:
- Press Control+Shift+P or Command+Shift+P to open the command palette.
- Search for "MCP: Add Server".
- Create a HTTP MCP server.
- Enter the URL
https://mcp.storage.dev/mcp. - Name the MCP server
tigris. - Authenticate with Tigris and get off to work!
Why are we doing this?
We want to make it easy for you to use Tigris any way you want: from the CLI, from the API, from the web, and from your agentic workflows. Hosting a copy of the Tigris MCP server means that you have even more flexibility when it comes to using Tigris. It also opens up the ability to use Tigris from the ChatGPT or Claude web views.
One of the roughest edges of using MCP servers is needing to install and update
the MCP server in order to run it. There’s tricks to this like using npx and
running update commands regularly, but one of the easiest ways to eliminate that
entire problem is to not require you to run the MCP server in the first place.
This makes you always have access to the most recent version of the MCP server
and you don’t need to take the risk involved with running software published by
a third party.
Even better, we implemented the MCP OAuth flow. This means you don’t even need to load API keys into your agent’s configuration, thus reducing the attack surface. We also took the chance to implement accessing multiple Tigris organizations at once with this new OAuth flow, meaning that you can get an even better experience with our hosted MCP server than you got with running the MCP server locally. If you ask your agent to list buckets, it’ll list them across all your organizations.
We need your help
Right now this is an experiment and in a public beta phase. We want to iterate and make this the best way to access object storage from your agents, but in order to do that we need your feedback on what you like and don’t like about it. If things break, please let us know so we can fix it for everyone.
Let’s see what we can cook up when we rethink the user experience of object storage from scratch.
AI-native object storage
Tigris makes it easy to use object storage from anywhere: from the admin console in a browser to the S3 API on your server, and now from any of your AI agents. Tigris makes your storage global out of the box and safe for access from multiple parallel agents with bucket forking.