6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Browse, move and share files on a Files.com site; manage users and permissions.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Files.com MCP server connects a Files.com managed file transfer site to Claude, ChatGPT and any MCP-compatible agent. Anthropic's directory lists 61 tools that browse and move files, read every audit log, build share links, and create or delete users, groups and folder permissions. Sign-in is OAuth, and the token carries your whole account.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
https://app.files.com/.well-known/oauth-protected-resource/api/ai/mcp/v1 declares resource, authorization_servers and bearer_methods_supported and no scopes_supported. Its authorization server metadata declares no scopes_supported either. Nothing in the grant separates reading a folder from deleting a user. The account you sign in as is the entire permission boundary.Delete_User, Delete_Group and Delete_Permission change who can reach the site, not just what is on it. Files.com's Restore feature covers deleted files, folders and users, so those are reversible by a Site Administrator within the retention window; we found no equivalent documented recovery for a deleted permission or share link.Delete_File.Create_Bundle_Recipient cannot be told not to send. The email is a hardcoded parameter in the published source, not a default you can override.Create_User and Update_User force SFTP, FTP, WebDAV and REST API access on. There is no way through these tools to make a user who can only use the web interface.https://app.files.com/api/ai/mcp/v1; Files.com's documentation tells you to use your own site hostname. The listed URL answers an OAuth challenge, so it is live, but a per-site deployment is what the vendor documents.readOnlyHint and destructiveHint annotations are advisory metadata for the client. Files.com's own package notes that many clients let you disable individual tools, and on this connector that client-side toggle is the only per-tool control that exists.tools/list. The endpoint returned 401 to an anonymous request, so the surface described here comes from the vendor's published source and Anthropic's directory, which agree. We could not confirm the hosted deployment runs version 1.0.80, and no prompts or resources capability could be observed either way.Yes. Six of the 61 tools carry a delete verb, and Delete_File is one of them. Files.com holds deleted files for a configurable window so a Site Administrator can restore them, and its documentation gives the default as 30 days. Setting that window to zero makes deletion permanent, and Files.com advises against it.
Yes, and nothing forces it to add protection. Create_Bundle takes password, expires_at and max_uses as optional parameters that all default to unset. A share link created without them is a URL anyone holding it can open without signing in, which makes it a credential in its own right.
Yes, always. The tool is named Create_Bundle_Recipient, which reads like adding a row to a list. The published source hardcodes share_after_create to true before calling the API, under a comment labelling it a smart default. There is no parameter that turns the email off, so every call to this tool sends mail.
None that narrow anything. Neither the server's RFC 9728 descriptor nor its OAuth authorization server metadata declared scopes_supported on 2026-08-22. Files.com documents the token as representing your login session, so the agent gets whatever you can do. Sign in as a site administrator and the agent inherits administrator rights.
Choose the account you sign in with. Files.com states the AI can perform the same actions as the account it authenticates with, so a regular non-admin user limits it to that user's folder permissions. There is no scope screen and no per-tool toggle at consent, so the account is the only boundary.
Yes. Create_Permission grants a user or group a named permission on a folder path, and the published source accepts admin among its values alongside full, readonly, writeonly, list and history. Delete_Permission removes one. Both run under whatever rights your signed-in account holds.
Your own site's hostname, not a shared one. Files.com documents the pattern as https://<mysite>.files.com/api/ai/mcp/v1/ or your custom domain with the same path. Anthropic's directory lists https://app.files.com/api/ai/mcp/v1, which returned an OAuth challenge on 2026-08-22, but the per-site form is what Files.com tells you to configure.
Your site refused to register the client. Files.com documents two causes: the client needs Dynamic Client Registration, which a Site Administrator must switch on because it ships disabled, or AI features are turned off site-wide. Claude Code, Claude desktop and mobile use CIMD instead and do not need that setting.
llms.txt index (retrieved 2026-08-22) · retrieved 2026-08-22files-com-mcp 1.0.80 wheel from PyPI, tool registrations in files_com_mcp/generated_tools/ and files_com_mcp/authored_tools/ (retrieved 2026-08-22). Vendor repository · retrieved 2026-08-22https://app.files.com/api/ai/mcp/v1 returned 401 with a www-authenticate header naming the RFC 9728 descriptor; the descriptor and https://app.files.com/.well-known/oauth-authorization-server were then read directly (2026-08-22) · retrieved 2026-08-22Connect Files.com once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.