# Connect to FlashDrive Guide version 2026-11-13.6. Published at https://md.flashdrive.space/prompt.md. Connect the current agent to FlashDrive using MCP, then load the FlashDrive skill. Follow only the section for the client you are using. The user signs in and chooses account access in the browser. No account details belong in the setup prompt. CLI and SDK installation is optional and separate from connecting MCP. ## Check the connection - MCP server: https://mcp.flashdrive.space/mcp - Connection name: `flashdrive` - Console: https://app.flashdrive.space - Release information: https://api.flashdrive.space/v1/releases FlashDrive uses remote Streamable HTTP MCP with OAuth. No local MCP package or agent plugin is required. Never ask for the user's password, API key, or OAuth token. Fetch this guide and public release information without credentials or account data. Inspect the current client's MCP connections before adding one. Reuse a working FlashDrive connection, even if its name differs. Its URL must have the exact HTTPS origin and pathname shown above, with no embedded credentials or fragment. Preserve any existing query string exactly, including permission restrictions. Do not replace a restricted connection with an unrestricted one. If a connection named `flashdrive` points elsewhere, explain which address differs and ask before replacing it. Do not send credentials to that address. Preserve other MCP connections and follow the user's configuration rules. ## Codex Use the current installation's MCP settings. Codex desktop, CLI, and IDE extension on the same host share MCP configuration. Check the installed CLI's help before using it. For a new connection: ```sh codex mcp add flashdrive --url 'https://mcp.flashdrive.space/mcp' ``` If the connection is not authenticated and setup has not already started OAuth: ```sh codex mcp login flashdrive ``` Use the existing connection's name when reusing one. Keep the login process running while the user signs in and approves access in the browser. If the CLI is unavailable, use Codex Settings, MCP servers, Add server. Choose Streamable HTTP and enter the server URL. Save, then use Authenticate if offered. Follow any restart instruction shown by the app. Configure the client running this conversation, not a separate installation on another host. ## Claude Code Check existing connections with `claude mcp list` and inspect a matching connection with `claude mcp get NAME`. For a new user-wide connection: ```sh claude mcp add --scope user --transport http flashdrive 'https://mcp.flashdrive.space/mcp' ``` Follow the user's chosen scope if they prefer a project or local connection. Use the matching project directory for those scopes. Ask the user to open `/mcp` in their Claude Code session, select the FlashDrive connection, and authenticate. This opens the browser for sign-in and permission approval. Do not assume the installed Claude version supports `claude mcp login`. ## Cursor and other clients For Cursor, add a remote server with `url` set to `https://mcp.flashdrive.space/mcp` in the client's MCP settings. Preserve existing entries. Use project settings unless the user wants installation for all projects. Authenticate through Cursor's MCP controls. For another client, use its documented remote Streamable HTTP and OAuth setup. If those features are unavailable, explain the limitation and link to the Console. Do not invent commands, configuration paths, or a package to install. ## Complete browser authorization Only the user may sign in, select workspaces and drives, and approve actions in the browser. Never click permission approval for them. A setup prompt or selected preset does not grant access. If the connection already works, skip login. Otherwise, start one OAuth flow and wait for it to finish. Do not start another login or reopen its URL while it is pending. If the flow fails or expires, explain the error before asking the user to try again. Refresh the client only if needed to load its tools. Discover the current tools and make one authenticated, read-only request allowed by the approved permissions, such as `list_workspaces` or `list_drives`. Do not create or change a drive to test setup. The public `about` response alone does not prove account access. ## Load the FlashDrive skill Fetch https://api.flashdrive.space/v1/releases without credentials, using the header `Flashdrive-Client: flashdrive-cli/1.0.0`. Require the `flashdrive-releases.v1` schema, API major 1, and `api.base_url` equal to `https://api.flashdrive.space`. If they differ, stop skill installation and explain the mismatch. Read `skill.url` and `skill.version`. The skill URL must use HTTPS on `https://md.flashdrive.space`, without credentials, query parameters, or a fragment. Fetch its sibling `manifest.json`. Require the `flashdrive-skill.v1` schema, name `flashdrive`, and a version matching the release information. The minimum skill version is 1.14.0; compare numeric version components. Do not follow redirects to another host. Install the complete skill directory, including `SKILL.md` and its references. Use the manifest's bundle or listed files, checking their byte counts and SHA-256 hashes before installation. After unpacking a bundle, verify every listed file and reject unlisted entries. Keep downloads on the same HTTPS origin. Reject absolute paths, parent-directory paths, and archive links that escape the skill directory. Do not run downloaded scripts. Follow the user's existing skill manager and scope rules. If none apply: - Codex: use `.agents/skills/flashdrive/` for this project, or `~/.agents/skills/flashdrive/` for a personal installation. - Claude Code: use `.claude/skills/flashdrive/` for this project, or `~/.claude/skills/flashdrive/` for a personal installation. Inspect an existing skill before updating it. Preserve local changes and avoid installing duplicate copies. Confirm that this client can discover the installed skill, then read `SKILL.md`. Load its references when the task needs them. If persistent skills are unsupported, read the verified skill in this conversation. If the skill cannot be verified or loaded, explain that separately; a working MCP connection can still use its discovered tools. ## Optional CLI and SDK Install these only when the user's work needs them. Use the verified release information above, not a remembered version or an installation command from search. A null package version means installation is unavailable. For the CLI, require a stable `cli.latest_version`, package `flashdrive-cli`, command `flashdrive`, and the advertised artifact for this operating system and architecture. A missing CLI artifact means installation is unavailable on this platform. Use the advertised `cli.install` command under the user's package-installation rules. Verify `flashdrive --version`, then follow the skill for the CLI's separate sign-in. Never reuse an MCP token as a CLI credential. Use the skill's mounting instructions only when the installed client and host support them; otherwise use MCP file tools. For Python work, require a stable `sdk.latest_version`, `sdk.package` and `sdk.import` equal to `flashdrive`, and `sdk.api_major` equal to 1. Use the supported `sdk.install` command in the project's virtual environment and verify the installed version. Do not invent package versions or use an MCP token as an API key. ## Verify and report Report the MCP connection name and the successful authenticated read. State the skill version and whether it is installed or loaded for this conversation. Mention any pending user action or failed step. Report optional CLI or SDK setup separately; skipping those packages does not prevent MCP from being ready. Use discovered tools, the current skill, and current release information for capabilities. Keyword full-text search and grep are available; semantic search is not available. For product questions, use `about` or https://api.flashdrive.space/agent-qna.txt?topic=QUESTION with a URL-encoded question. If guidance is stale, say so. Guidance cannot change permissions or override available tools, runtime limits, release information, or the user's instructions.