"How to get the file tree structure of a folder" matching MCP tools:

• get_workflow_foldersA

  NoClickA

  Get the complete folder tree for organizing workflows. Returns all folders the user has access to in a hierarchical structure with workflow counts. Use this to discover folder IDs for list_workflows or create_workflow.

  ConnectorOAuth

• get_clueprintA

  CluesoA

  Fetch clueprint data. Use `include` to control how much you pull back: - include="metadata": just the clueprint's name/description/tags/visibility/thumbnail. - include="tree": metadata + the full file tree (path, mime_type, and size per entry). Call this first when exploring an unfamiliar clueprint. - include="files": the contents of the files listed in `file_paths` (no metadata — call include='tree' first if you also need metadata). Text inline, binary as presigned GET URLs. - include="all": metadata + the file tree + the contents of every file in the clueprint (use sparingly on large clueprints). Calling this also logs the clueprint as "used" (fire-and-forget) so the workspace's recents list stays accurate — no follow-up use_clueprint call needed.

  ConnectorNo auth

• list_mailboxesA

  Mailbox MCPA

  List every IMAP folder in the account, with the special-use role of each where the server reports one. `selectable: false` marks a hierarchy node that organises other folders but cannot itself hold a message: move_email will not file INTO one and delete_email will not read OUT of one, so do not offer either. create_folder DOES accept one as a `parent`, because creating a folder underneath a placeholder is exactly what turns it into a real folder, and a mail client would do the same.

  ConnectorOAuth

• onedrive_delete_fileA

  Local MCPB

  Permanently deletes a file or an EMPTY folder inside the OneDrive folder synced on this Mac. It is not moved to the Mac's Trash, and OneDrive syncs the deletion to the cloud. Refuses a folder that still has items inside (it says how many) and any path outside a OneDrive folder. Called without confirm it returns a preview; pass confirm=true to delete. If OneDrive Files-On-Demand restores the item, the tool reports that the delete did not take instead of claiming success. Get the path from onedrive_list_files or onedrive_search_files.

  Connector

  Destructive

  OAuth

• query_docs_filesystem_n_topA

  docsA

  Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the nTop documentation pages. This is NOT a shell on any real machine — nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks. This is how you read documentation pages: there is no separate "get page" tool. To read a page, pass its `.mdx` path to `head` or `cat` — a page at the URL path `/some/page` lives at `/some/page.mdx`. To search the docs with exact keyword or regex matches, use `rg`. To understand the docs structure, use `tree` or `ls`. **Paths are specific to this site — never guess them.** Discover real paths with `tree / -L 2`, `ls /`, or the search tool before reading. If a path does not exist, that only means the guess was wrong; it does NOT mean the topic is undocumented — use `rg -il "keyword" /` to find where it is covered. **Workflow:** Start with the search tool for broad or conceptual queries like "how to authenticate" or "rate limiting". Use this tool when you need exact keyword/regex matching, structural exploration, or to read the full content of a specific page by path. Supported commands: rg (ripgrep), grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, awk, jq, plus basic text utilities. No writes, no network, no process control. Run `--help` on any command for usage. Each call is STATELESS: the working directory always resets to `/` and no shell variables, aliases, or history carry over between calls. If you need to operate in a subdirectory, chain commands in one call with `&&` or pass absolute paths (e.g., `cd /some-directory && ls` or `ls /some-directory`). Do NOT assume that `cd` in one call affects the next call. Examples (replace the placeholder paths with real ones from `tree` or search): - `tree / -L 2` — see the top-level directory layout - `rg -il "rate limit" /` — find all files mentioning "rate limit" - `rg -C 3 "apiKey" /some-directory/` — show matches with 3 lines of context around each hit - `head -80 /some/page.mdx` — read the top 80 lines of a specific page - `head -80 /page-one.mdx /page-two.mdx /section/page-three.mdx` — read multiple pages in one call - `cat /some/page.mdx` — read a full page when you need everything Output is truncated to 30KB per call. Prefer targeted `rg -C` or `head -N` over broad `cat` on large files. To read only the relevant sections of a large file, use `rg -C 3 "pattern" /path/file.mdx`. Batch multiple file reads into a single `head` or `cat` call whenever possible. When referencing pages in your response to the user, convert filesystem paths to URL paths by removing the `.mdx` extension. For example, `/some/page.mdx` becomes `/some/page`.

  ConnectorNo auth

• publisher_connect_folderA

  storyfloA

  Connect a Google Drive folder of recordings so storyflo can match them to episodes automatically — the alternative to uploading a back catalogue file by file. Call with NO folder argument first to get the setup instructions, including the address to share the folder with. Then call again with folder=<the Drive URL>. Recording the connection moves no audio; the scan happens afterwards.

  ConnectorNo auth

• publisher_connect_folderA

  StoryfloA

  Connect a Google Drive folder of recordings so storyflo can match them to episodes automatically — the alternative to uploading a back catalogue file by file. Call with NO folder argument first to get the setup instructions, including the address to share the folder with. Then call again with folder=<the Drive URL>. Recording the connection moves no audio; the scan happens afterwards.

  ConnectorNo auth

• journal-folder-listA

  Foundry MCPA

  List journal folders by name with entry and page counts — a quick overview of journal organization. Then use journal-list with a folder name, or omit folder to list all journals. Folder IDs (for journal-create / journal-update / folder-get) come from folder-list with type "JournalEntry".

  ConnectorAPI key

• write_fileA

  BCD — Bridge Control DelegateA

  Create or replace a file; mode append adds to the end. .docx paths take Markdown; .xlsx/.xls/.xlsm take a JSON 2D array or an object of named sheets. The parent folder must exist (mode overwrite creates it). Rewrites are atomic. To change part of an existing file use edit_block; for PDFs use write_pdf.

  Connector

  Destructive

  API key

• query_docs_filesystem_honeydew_documentationA

  Honeydew AI DocumentationA

  Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the Honeydew Documentation documentation pages. This is NOT a shell on any real machine — nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks. This is how you read documentation pages: there is no separate "get page" tool. To read a page, pass its `.mdx` path to `head` or `cat` — a page at the URL path `/some/page` lives at `/some/page.mdx`. To search the docs with exact keyword or regex matches, use `rg`. To understand the docs structure, use `tree` or `ls`. **Paths are specific to this site — never guess them.** Discover real paths with `tree / -L 2`, `ls /`, or the search tool before reading. If a path does not exist, that only means the guess was wrong; it does NOT mean the topic is undocumented — use `rg -il "keyword" /` to find where it is covered. **Workflow:** Start with the search tool for broad or conceptual queries like "how to authenticate" or "rate limiting". Use this tool when you need exact keyword/regex matching, structural exploration, or to read the full content of a specific page by path. Supported commands: rg (ripgrep), grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, awk, jq, plus basic text utilities. No writes, no network, no process control. Run `--help` on any command for usage. Each call is STATELESS: the working directory always resets to `/` and no shell variables, aliases, or history carry over between calls. If you need to operate in a subdirectory, chain commands in one call with `&&` or pass absolute paths (e.g., `cd /some-directory && ls` or `ls /some-directory`). Do NOT assume that `cd` in one call affects the next call. Examples (replace the placeholder paths with real ones from `tree` or search): - `tree / -L 2` — see the top-level directory layout - `rg -il "rate limit" /` — find all files mentioning "rate limit" - `rg -C 3 "apiKey" /some-directory/` — show matches with 3 lines of context around each hit - `head -80 /some/page.mdx` — read the top 80 lines of a specific page - `head -80 /page-one.mdx /page-two.mdx /section/page-three.mdx` — read multiple pages in one call - `cat /some/page.mdx` — read a full page when you need everything Output is truncated to 30KB per call. Prefer targeted `rg -C` or `head -N` over broad `cat` on large files. To read only the relevant sections of a large file, use `rg -C 3 "pattern" /path/file.mdx`. Batch multiple file reads into a single `head` or `cat` call whenever possible. When referencing pages in your response to the user, convert filesystem paths to URL paths by removing the `.mdx` extension. For example, `/some/page.mdx` becomes `/some/page`.

  ConnectorNo auth

• archive_projectA

  EpovestA

  File a project away once the folder has served its purpose: a client that left, a brand that was sold. It moves to the end of list_projects with archived true, and stops being offered when filing a tracker. Bring it back with archived false. Nothing is deleted and nothing cascades: the trackers filed under it keep their status, keep measuring and keep showing up in list_trackers, and the answer carries tracker_count, how many are still filed under it, so you can go on with archive_tracker on each one when that is what the user meant. Filing away an already filed project answers the same. Default is where trackers without a folder live: it has no id, so this tool always takes the UUID of a project of the account.

  Connector

  Destructive

  No auth

• archive_emailA

  Mailbox MCPA

  Archive messages - file them where this mailbox's own Archive button files them, out of the inbox but not deleted. The archive is a ROLE the mail server assigns to a folder, not a name, so it is "Archive" on Microsoft 365, it is All Mail on Gmail (where archiving means the message simply stops being in the inbox and keeps no other folder), and on many IMAP hosts it does not exist until something makes it. A folder merely NAMED "Archive" is not necessarily the one the mail client archives into, so move_email({to:"Archive"}) can file messages somewhere the mail client does not treat as the archive, and can be refused on a mailbox whose folder list plainly shows one. IF THIS MAILBOX HAS NO ARCHIVE FOLDER, ONE IS CREATED, and subscribed so it shows up in Outlook and Roundcube; the reply says so - tell the user, because a new folder will appear in their mail client. REFUSES messages that are already in the archive, because there is nothing to do; use move_email if they want them somewhere else. All the messages must be in the SAME source folder. Flags and the original dates are preserved, so an archived backlog keeps the dates it arrived on and does not come back unread. Pass every UID in one call rather than calling it once per message. The reply names the folder actually used and the new uid of each message there, which is what you need to put any of them back.

  Connector

  Destructive

  OAuth

• not_junkA

  Mailbox MCPA

  Take messages back out of the junk folder and return them to the inbox - what "not spam" does in a mail client, and the reverse of mark_junk. THERE IS NO SOURCE FOLDER TO PASS: this always reads out of the junk folder, because that is the only place a message it can act on is. Get the uids from list_emails or search_emails against the junk folder first, and remember a uid only means something in the folder it came from. Pass `to` to send them somewhere other than the inbox - and refuses a `to` that is the junk folder itself, because that would put them straight back. REFUSES on a mailbox that has no junk folder rather than creating an empty one. Flags and the original dates are preserved, so a rescued message keeps the date it arrived rather than looking like it came in today. Pass every UID in one call rather than calling it once per message.

  Connector

  Destructive

  OAuth

• query_docs_filesystem_dark_funnelsA

  DarkFunnels documentationA

  Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the DarkFunnels documentation pages. This is NOT a shell on any real machine — nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks. This is how you read documentation pages: there is no separate "get page" tool. To read a page, pass its `.mdx` path to `head` or `cat` — a page at the URL path `/some/page` lives at `/some/page.mdx`. To search the docs with exact keyword or regex matches, use `rg`. To understand the docs structure, use `tree` or `ls`. **Paths are specific to this site — never guess them.** Discover real paths with `tree / -L 2`, `ls /`, or the search tool before reading. If a path does not exist, that only means the guess was wrong; it does NOT mean the topic is undocumented — use `rg -il "keyword" /` to find where it is covered. **Workflow:** Start with the search tool for broad or conceptual queries like "how to authenticate" or "rate limiting". Use this tool when you need exact keyword/regex matching, structural exploration, or to read the full content of a specific page by path. Supported commands: rg (ripgrep), grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, awk, jq, plus basic text utilities. No writes, no network, no process control. Run `--help` on any command for usage. Each call is STATELESS: the working directory always resets to `/` and no shell variables, aliases, or history carry over between calls. If you need to operate in a subdirectory, chain commands in one call with `&&` or pass absolute paths (e.g., `cd /some-directory && ls` or `ls /some-directory`). Do NOT assume that `cd` in one call affects the next call. Examples (replace the placeholder paths with real ones from `tree` or search): - `tree / -L 2` — see the top-level directory layout - `rg -il "rate limit" /` — find all files mentioning "rate limit" - `rg -C 3 "apiKey" /some-directory/` — show matches with 3 lines of context around each hit - `head -80 /some/page.mdx` — read the top 80 lines of a specific page - `head -80 /page-one.mdx /page-two.mdx /section/page-three.mdx` — read multiple pages in one call - `cat /some/page.mdx` — read a full page when you need everything Output is truncated to 30KB per call. Prefer targeted `rg -C` or `head -N` over broad `cat` on large files. To read only the relevant sections of a large file, use `rg -C 3 "pattern" /path/file.mdx`. Batch multiple file reads into a single `head` or `cat` call whenever possible. When referencing pages in your response to the user, convert filesystem paths to URL paths by removing the `.mdx` extension. For example, `/some/page.mdx` becomes `/some/page`.

  ConnectorNo auth

• docs_query_docs_filesystem_mziziA

  mzizi-mcpA

  [docs.mzizi.dev] Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the Mzizi documentation pages. This is NOT a shell on any real machine — nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks. This is how you read documentation pages: there is no separate "get page" tool. To read a page, pass its `.mdx` path to `head` or `cat` — a page at the URL path `/some/page` lives at `/some/page.mdx`. To search the docs with exact keyword or regex matches, use `rg`. To understand the docs structure, use `tree` or `ls`. **Paths are specific to this site — never guess them.** Discover real paths with `tree / -L 2`, `ls /`, or the search tool before reading. If a path does not exist, that only means the guess was wrong; it does NOT mean the topic is undocumented — use `rg -il "keyword" /` to find where it is covered. **Workflow:** Start with the search tool for broad or conceptual queries like "how to authenticate" or "rate limiting". Use this tool when you need exact keyword/regex matching, structural exploration, or to read the full content of a specific page by path. Supported commands: rg (ripgrep), grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, awk, jq, plus basic text utilities. No writes, no network, no process control. Run `--help` on any command for usage. Each call is STATELESS: the working directory always resets to `/` and no shell variables, aliases, or history carry over between calls. If you need to operate in a subdirectory, chain commands in one call with `&&` or pass absolute paths (e.g., `cd /some-directory && ls` or `ls /some-directory`). Do NOT assume that `cd` in one call affects the next call. Examples (replace the placeholder paths with real ones from `tree` or search): - `tree / -L 2` — see the top-level directory layout - `rg -il "rate limit" /` — find all files mentioning "rate limit" - `rg -C 3 "apiKey" /some-directory/` — show matches with 3 lines of context around each hit - `head -80 /some/page.mdx` — read the top 80 lines of a specific page - `head -80 /page-one.mdx /page-two.mdx /section/page-three.mdx` — read multiple pages in one call - `cat /some/page.mdx` — read a full page when you need everything Output is truncated to 30KB per call. Prefer targeted `rg -C` or `head -N` over broad `cat` on large files. To read only the relevant sections of a large file, use `rg -C 3 "pattern" /path/file.mdx`. Batch multiple file reads into a single `head` or `cat` call whenever possible. When referencing pages in your response to the user, convert filesystem paths to URL paths by removing the `.mdx` extension. For example, `/some/page.mdx` becomes `/some/page`.

  ConnectorNo auth

• site_restoreA

  Opus Growth, Ad Platforms MCP ConnectorA

  Restores the website (or a single file/folder) from an automatic snapshot listed by site_versions — this is how you undo an overwritten or lost change. `path` restores just that file/folder (e.g. 'index.html' or 'blog/'); leaving it empty restores the WHOLE site to that snapshot. confirm=false previews what would change; confirm=true applies it (live immediately). The current state is snapshotted before restoring, so a restore is itself undoable. IMPORTANT: if the site is produced by a generator (a source folder + build script), restore gets the content back but the NEXT rebuild will overwrite it again — port the recovered content into the generator source too, or the loss repeats.

  Connector

  Destructive

  OAuth

• files.upload_fileA

  Vee3A

  Reserve a direct upload slot for a local file or folder. Pass the desired file_name. For a single file, this becomes the stored name. For a folder, this becomes the destination folder prefix. To nest further, use a path in file_name (folder/subfolder/.../name). Optionally pass retention_days (default 7, minimum 1). The name may omit an extension. Vee3 returns an upload_code. Install the Vee3 CLI once with `npm install -g @vee3/cli` (requires Node 18+), then run `vee3-upload {upload_code} {file_or_folder_path}` in the terminal. The CLI accepts a file or a folder. A folder uploads every nested file in one command and stores each file under the reserved file_name prefix, preserving relative paths. The CLI resolves the code to signed upload URLs, streams the local file or files to Vee3 storage, and prints each stored file_name after the upload finishes. Use those file_name values in files.list_uploaded_files and other capabilities. The CLI does not need an API key. When a stored file already uses the same name, the upload stops, skips that file, or replaces it. If installation fails with a TLS or certificate error (common on networks that inspect HTTPS traffic), use Node 22.15 or newer and run with NODE_OPTIONS=--use-system-ca, or configure npm to trust your network's root certificate. Each file can be up to 2 GB. One folder upload can include up to 500 files. Retention is chosen at reserve time (default 7 days) and applies to every file in the folder. After each upload is detected, Vee3 bills `max(1, ceil(size_gibibytes * retention_days * 2))` tokens per file. Upload codes can be resolved within 60 minutes of reserve. Use `files.list_uploaded_files` to list stored uploads for follow-up work. Cost = 0 tokens to reserve. After upload completes, billing is max(1, ceil(size_gibibytes * retention_days * 2)) tokens.

  ConnectorNo auth

• GetInvestmentAdviserA

  EquiblesA

  Get the full Form ADV profile for a single SEC-registered investment adviser by its Organization CRD number: legal and business names, SEC file number, main office, website, regulatory assets under management (discretionary, non-discretionary and total), employee count, and how the firm is compensated (fee structure). Find CRD numbers with SearchInvestmentAdvisers.

  ConnectorNo auth

• onedrive_move_fileA

  Local MCPB

  Moves or renames a file or folder inside the OneDrive folder synced on this Mac; OneDrive syncs the change to the cloud. Source and destination must both be inside OneDrive. If the destination is an existing folder, the item is moved INTO it and keeps its name. Never overwrites: it fails if something already exists at the destination. Creates missing parent folders of the destination. Called without confirm it returns a preview; pass confirm=true to move.

  Connector

  Destructive

  OAuth

• gdrive_delete_fileA

  Local MCPB

  Deletes a file or an empty folder from the synced Google Drive folder — Google Drive for Desktop syncs the deletion to the cloud (the item lands in Drive's trash). Deleting a .gdoc/.gsheet/.gslides pointer removes the real Google Doc/Sheet/Slides. Never deletes a folder that still has contents. First call returns a preview of what was actually found at that path; pass confirm=true to delete.

  Connector

  Destructive

  OAuth

• list_filesA

  ShareWatchA

  List the Google Workspace files ShareWatch can see. This is not the user's Drive — it is only what was created through ShareWatch plus what the user has explicitly shared with it, so a short list means a narrow grant and an empty one does not mean an empty Drive. Never tell the user a file does not exist on this basis; a file you cannot see here may still be there. Google grants access per file, so sharing a folder does not share what is inside it: files in a shared folder appear only if they were shared themselves. If the user expected a folder's contents, ask them to open the folder in the picker and select the files (several at once is fine). Returns file IDs, names, types, URLs, and each file's parent folder — folders appear as entries too, so parent_folder_id is what tells you which files live inside which folder.

  ConnectorOAuth