agentdrive

Guide

Add file storage to a custom agent with MCP

Point your agent's MCP client at https://useagentdrive.com/mcp. The server speaks Streamable HTTP and standard OAuth. Any MCP client library that supports both connects without code specific to agentdrive.

  1. Get your free drive

    Sign in at useagentdrive.com/signin. Your first drive is created for you: 500 MB, 25 MB per file.

    Get a free drive
  2. Point your MCP client at the server

    Use the Streamable HTTP transport with this URL. A request without a token returns 401 and names the discovery document.

    Transport: Streamable HTTP
    URL: https://useagentdrive.com/mcp
  3. Let the client discover and register

    Your client reads the two metadata documents, then registers itself as a public client. No client secret is issued.

    https://useagentdrive.com/.well-known/oauth-protected-resource/mcp
    https://useagentdrive.com/.well-known/oauth-authorization-server
  4. Authorize in the browser

    The flow is authorization code with PKCE S256. The human picks a drive and clicks Allow access.

    resource=https://useagentdrive.com/mcp
    scope=drive
    code_challenge_method=S256
  5. Call the tools

    Save a file and check the result. Only status=saved confirms a save.

    save_file  name="hello.md"  content="# hello"  mime_type="text/markdown"

What to know about tokens

The access token lasts until the owner revokes it. No refresh token is issued and none is needed.

A token opens one drive: the one the human picked. Browser cookies and drive URLs never authorize MCP requests.

Reconnecting the same client to the same drive replaces its older connection.

The five tools

save_file takes name and content, with encoding utf8 or base64. An optional request_id prevents duplicates on retries.

list_files pages with offset and limit. read_file reads whole or in chunks. get_file_link returns a browser link.

delete_file removes a file for good and revokes its link. Ask the human before deleting.

Questions

Is there an API key option?
No. Access is OAuth only, so a human approves each agent and can revoke it.
Does it support dynamic client registration?
Yes. Clients register at the registration endpoint named in the discovery document. Only public clients are supported.
Can my agent run without a human present?
After the first authorization, yes. The token keeps working until revoked, so later runs need no browser.
Is there an SDK to install?
No. Any MCP client library that supports Streamable HTTP and OAuth works. The plain-text reference is at /agent.

Other guides