Files.com

@Files.com list all folders under /projects/q1-launch and show me which ones have been modified in the last 7 days

Found 8 folders under /projects/q1-launch. Three have recent activity: /projects/q1-launch/design (modified 2 days ago, 14 files), /projects/q1-launch/marketing-assets (modified 4 days ago, 22 files), and /projects/q1-launch/legal-review (modified 6 days ago, 3 files). The remaining folders—/archived, /drafts, /feedback, /research, /templates—have not been touched in over two weeks. This is an illustrative example; actual folder counts and timestamps depend on your Files.com account state.

This example shows the MCP's folder-listing capability paired with AI reasoning to filter by recency. The MCP returns raw folder metadata; the AI interprets modification timestamps. Requires read permissions on the parent path. Large directory trees may hit pagination limits—results are returned in pages, so deep hierarchies take multiple calls.

@Files.com create a share link for /reports/2024-annual-financials.pdf that expires in 48 hours and requires a password

Share link created: https://yourcompany.files.com/share/a7f3k9m2 (expires in 48 hours). Password protection enabled—recipients must enter the password you set to access the file. This link grants view-only access to /reports/2024-annual-financials.pdf. This is an illustrative example; the actual share URL and expiration behavior depend on your Files.com account settings and the file's current permissions.

This example demonstrates the MCP's ability to generate time-limited, password-protected share links—a common workflow for sensitive document distribution. The MCP creates the share; you must communicate the password separately. Be aware that share creation is a write action with audit trail implications. If your account enforces IP restrictions or SSO, recipients may face additional access hurdles.

@Files.com show me all permissions on /contracts/vendor-agreements and identify any external users who have write access

Retrieved 12 permissions on /contracts/vendor-agreements. Two external users have write access: jane.doe@external-vendor.com (granted 14 days ago by admin@yourcompany.com) and contractor@freelance.net (granted 3 months ago, no expiration set). The remaining 10 permissions are internal team members with read-only access. This is an illustrative example; actual permission counts and user emails depend on your Files.com account configuration.

This example pairs the MCP's permission-listing tool with AI analysis to surface security-relevant details—external write access is a common audit concern. The MCP returns permission records; the AI filters by user domain and access level. Useful for compliance reviews, but note that permission changes made outside this session won't appear until the next query. Requires admin-level API key to list permissions on shared resources.

When Files.com wins for time-boxed external sharing

A 6-person creative agency ships final assets to clients every week—PSDs, video renders, brand guidelines. They need share links that expire after 7 days and can be revoked mid-flight if a client ghosts on payment. Files.com's Delete Share tool lets the team script link revocation from Switchy without logging into a dashboard. The List Permissions tool confirms who still has access before the next handoff. This works when your team sends 10-50 packages a month and needs audit trails. If you're just dropping occasional Dropbox links, the API key overhead isn't worth it. But if you're billing clients per deliverable and need programmatic control over access windows, this MCP turns share-link hygiene into a one-line Switchy command instead of a manual checklist.

Revoking access across 40 freelancers without clicking

A 12-person product studio cycles through 30-40 contractors per quarter—designers, copywriters, QA testers. Each gets folder permissions for their project scope, then needs clean removal when the contract ends. The Delete Permission tool lets the ops lead script bulk revocations from Switchy instead of hunting through Files.com's UI for each user. List Groups and List Permissions confirm the current state before the purge runs. This pays off when you onboard or offboard more than 5 people a week. Below that threshold, manual clicks are faster than maintaining API keys. Above it, this MCP turns a 90-minute monthly audit into a 5-minute Switchy query. The trade-off: you need someone comfortable writing the revocation logic, not just running pre-built scripts.

When programmatic file hosting beats manual S3 wrangling

A 4-person support team maintains a public knowledge base with 200+ PDF guides and video walkthroughs. Every doc update means uploading the new version, grabbing the public URL, and pasting it into their help center CMS. The Get S3 Key for Upload tool lets them script the upload-to-URL pipeline from Switchy—drop the file, get the link, done. List Folders confirms the staging structure before the upload runs. This makes sense when you're publishing 10+ files a week and the manual upload-copy-paste loop is eating 20 minutes per session. If you're updating docs monthly, the API setup cost outweighs the time saved. But if file hosting is a daily chore and your team already lives in Switchy for other workflows, this MCP collapses three tools into one command.