Tigris MCP Server

dev.storagePublished by storage.devOfficial publisherv1.14.2Updated Nov 4, 2026

Tigris MCP Server seamlessly connects AI agents to Tigris bucket and object management.

VerifiedStreamable HTTPWeb executableFiles & Storage

Overview

AI-generated overview

Remote MCP endpoint that connects AI assistants to Tigris for bucket and object management in cloud object storage.

What you can do
  • Manage Tigris buckets: create, list and configure storage buckets.
  • Manage objects: upload, list, retrieve and remove objects stored in buckets.
  • Work with Tigris object storage directly from an assistant over a hosted remote endpoint.
When to use it
Useful when you want an assistant to inspect or organize data held in Tigris object storage, such as listing buckets, checking objects, or moving files, without writing storage API calls yourself.
Requirements
A remote MCP endpoint at mcp.storage.dev using streamable HTTP; no local package or runtime is needed. Authentication is OAuth and required, so a Tigris account with access to the relevant buckets is needed, plus network access.
Before you install
OAuth grants the assistant access to your Tigris storage, and bucket and object operations can create, change or delete stored data. Review the scopes granted during sign-in and confirm which buckets are reachable before letting an assistant modify or remove objects.

Installation

In SourceWeft

  1. Open Tigris MCP Server in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.storage%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "tigris": {
      "type": "http",
      "url": "https://mcp.storage.dev/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

3
  1. v1.14.2LatestNov 4, 2026
  2. v1.14.1Nov 3, 2026
  3. v1.14.0Sep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Storage integrations