# agentdrive (useagentdrive.com) [Health: Active]

**Category:** 📂 File Systems  
**Repository:** https://useagentdrive.com/  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 1  
**Directory Page:** https://allmcps.com/mcp/agentdrive-useagentdrive-com

## Description
Persistent file storage for AI agents. Save files over MCP, get a link a human can open. Hosted remote MCP server at https://useagentdrive.com/mcp (Streamable HTTP, OAuth 2.1). Tools: save_file, list_files, read_file, get_file_link, delete_file.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "agentdrive-useagentdrive-com": {
    "url": "https://useagentdrive.com/mcp"
  }
}
```

## Documentation

## What agentdrive (useagentdrive.com) does

agentdrive provides persistent file storage for AI agents over the Model Context Protocol. Instead of keeping files only within an agent's immediate execution context, an agent can send files to the hosted service and retrieve them later through MCP tools. The service also supports generating a link that a human can open.

The available operations cover the basic file lifecycle: saving new files, browsing stored files, reading file contents, obtaining a human-openable link, and deleting files. This makes agentdrive a fit for workflows where an agent needs to preserve generated output, exchange files with a person, or access previously saved content during a later task.

## How it works

agentdrive is accessed as a remote MCP server rather than as a local process. Connect an MCP client to the Streamable HTTP endpoint:

`https://useagentdrive.com/mcp`

Authentication uses OAuth 2.1. After the client completes the service's authorization flow, the agent can invoke the exposed file-management tools over the MCP connection. File operations remain centered on the hosted service, so the agent interacts with stored files through tool calls rather than relying on a local filesystem integration.

## Setup and configuration

Configure an MCP-compatible client with the agentdrive endpoint and its OAuth 2.1 authentication flow. The connection URL is:

`https://useagentdrive.com/mcp`

Because the service is hosted and accessed over Streamable HTTP, setup consists of connecting the client to the remote endpoint and authorizing access. No local package or runtime configuration is required by the hosted endpoint. Environment variables are not needed for the standard remote connection.

## Tools and capabilities

agentdrive exposes these MCP tools:

- `save_file` stores a file for later access.
- `list_files` retrieves the files available in storage.
- `read_file` reads a stored file.
- `get_file_link` produces a link that a human can open.
- `delete_file` removes a stored file.

Together, these tools support both agent-only file handling and handoffs from an agent to a person. For example, an agent can save generated output, locate it later, read it back into a workflow, and provide a link for human access.

## Limitations and notes

agentdrive is centered on hosted file storage and exposes file lifecycle operations rather than general local filesystem access. Its remote connection requires an MCP client that can use Streamable HTTP and complete OAuth 2.1 authorization. The service endpoint is specific to agentdrive: `https://useagentdrive.com/mcp`.

_Full upstream README: https://allmcps.com/mcp/agentdrive-useagentdrive-com/readme_