uldl

sh.uldlPublished by uldl.shOfficial publisherv0.1.0Updated Oct 24, 2026

Persistent file storage for AI agents via MCP and curl. Upload, download, and version files.

VerifiedStreamable HTTPWeb executableFiles & StorageKnowledge & Memory

Overview

AI-generated overview

Gives an AI assistant persistent file storage: upload, download, and version files through a hosted uldl.sh endpoint.

What you can do
This is a remote MCP server for persistent file storage aimed at AI agents. According to the description, it lets an assistant upload, download, and version files, and the same storage is also reachable over curl. No individual tools are listed in the manifest, so the exact tool names and parameters are not documented here.
When to use it
Worth adding when an assistant needs to keep files between sessions or hand files to and from other tools, rather than working only in memory. It suits workflows where versioned uploads and downloads matter.
Requirements
A remote endpoint at uldl.sh reached over streamable HTTP. Authentication is required: a bearer access key sent in the Authorization header and your uldl.sh username sent in the x-uldl-username header. No local runtime or environment variables are declared.
Before you install
The server requires a bearer access key in the Authorization header; treat it as a secret and avoid exposing it in logs or shared configuration. Uploads and versioning write data to a third-party hosted service, so consider what files you send and who can read them.

Installation

In SourceWeft

  1. Open uldl in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/sh.uldl%2Fuldl/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.

{
  "mcpServers": {
    "uldl": {
      "type": "http",
      "url": "https://uldl.sh/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

67% 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.