Use the endpoint above—never your password or an API key.
One archive · any compatible agent
Connect your AI to DiskDrive.
DiskDrive is built to be used by your assistant. Connect once through the open Model Context Protocol, choose what it may access, then let it save, search, and remember on your behalf.
https://mcp.diskdrive.ai/mcpDiskDrive shows the exact read and write permissions requested.
Your assistant chooses the appropriate DiskDrive tool.
Choose your assistant
Connection instructions
These setup paths follow each client's current MCP documentation. A dated badge means its complete OAuth and tool flow was exercised live against DiskDrive; all other named clients remain candidates.
Let Muse build the connector
- Copy the setup message below and paste it into Muse. Muse should present a secure Connect card—not ask you for a token.
- Choose Connect once, sign in to DiskDrive in the browser, review the requested permissions, and authorize the connector. DiskDrive now coalesces an identical registration repeated immediately by the same public connector so a second permission review is not required.
- In our live test, Muse 4.1 began sending a non-JWT credential after refreshing at about 15–20 minutes. If status returns 401, reconnect once. This is a known Muse compatibility issue, not something you configured incorrectly.
Let Codex connect itself
- Copy the setup message below and paste it into a Codex task. The message tells Codex what to do—it is not technical work for you.
- If DiskDrive is missing, Codex will ask permission to add it. Approve that specific settings change.
- Restart Codex once only if it just added DiskDrive. If DiskDrive was already present but failed to load, Codex will diagnose the failure instead of asking you to restart again.
Use the optional command line
- Use this path only if the codex command already works in your terminal.
- Run both commands, then complete the DiskDrive authorization in your browser.
- Restart Codex before testing the connection in a new task.
codex mcp add diskdrive --url https://mcp.diskdrive.ai/mcp
codex mcp login diskdrive --oauth-client-registration cimdConnect from the Hermes CLI
- Run these commands on the computer where you use Hermes. The cimd setting selects Hermes' supported dynamic-registration fallback for its current client metadata.
- Complete the DiskDrive sign-in and permission review in your browser.
- Confirm the test reports 15 tools, then start Hermes Chat and run /reload-mcp.
hermes config set mcp_servers.diskdrive.url https://mcp.diskdrive.ai/mcp
hermes config set mcp_servers.diskdrive.auth oauth
hermes config set mcp_servers.diskdrive.oauth.cimd false
hermes mcp login diskdrive
hermes mcp test diskdriveAdd a custom connector
- Open Customize → Connectors and choose Add custom connector.
- Name it DiskDrive and paste https://mcp.diskdrive.ai/mcp.
- Choose Connect, sign in to DiskDrive, review the requested permissions, and enable it in a conversation.
Add a remote HTTP server
- Run the command below in a terminal.
- Run the login command to complete browser authorization, then use claude mcp get diskdrive to verify the connection.
- Keep tool approvals enabled until you are comfortable with write operations.
claude mcp add --transport http --scope user diskdrive https://mcp.diskdrive.ai/mcp
claude mcp login diskdriveCreate a developer connection
- In ChatGPT, open Settings → Security and login and enable Developer mode.
- Open Plugins, select the plus button, and create a connection named DiskDrive.
- Paste https://mcp.diskdrive.ai/mcp, then link your DiskDrive account when ChatGPT asks to authenticate.
Add a Streamable HTTP server
- First finish Gemini CLI's own Google or API-key sign-in, then run the command below from a trusted local terminal.
- Start Gemini CLI and run /mcp auth diskdrive.
- Complete browser authorization, then use /mcp to verify the tools are connected.
gemini mcp add --transport http --scope user diskdrive https://mcp.diskdrive.ai/mcpAdd a remote MCP server
- Open Cursor Settings → Tools & MCP and add a new remote server.
- Use DiskDrive as the name and https://mcp.diskdrive.ai/mcp as the Streamable HTTP URL.
- Choose Connect or Authenticate, then approve access in the DiskDrive browser window.
Every other compatible assistant
Use the generic MCP connection
If your AI is not listed above, look for “MCP,” “custom connector,” “remote tools,” or “add server” in its settings. Supply these four values and let the client discover the rest.
- Name
- DiskDrive
- URL
- https://mcp.diskdrive.ai/mcp
- Transport
- Streamable HTTP
- Authentication
- OAuth 2.1 with browser sign-in
After connecting
Try a natural request
If your client displays MCP prompts, choose “Test my DiskDrive connection” for a guided save, search, and Memory check.
- “Search my DiskDrive for the proposal and summarize it.”
- “Remember that I prefer concise weekly project updates.”
- “List the files in my DiskDrive before changing anything.”
- “Save this note as Markdown in /AI, then confirm when scanning is complete.”