MCP server file sharing AI agents: a safety guide
What Tarkle's MCP server lets an AI assistant do with client files, and a four-step checklist before you connect.
An MCP server lets an AI assistant work with your files through a fixed set of actions you can read in advance. For an agency, MCP server file sharing AI agents comes down to one question: which actions do you hand over, and to which account? This guide explains what an MCP connection is, which tasks suit it, and a four-step safety checklist to run before you connect anything to client files.
What an MCP connection is
MCP stands for Model Context Protocol. It is an open-source standard for connecting AI applications to external systems, as its maker describes it. The assistant does not get a free run of the product. It can only use the tools the server offers.
Tarkle's MCP server lets AI assistants list your files, upload, create transfers and request files, through the Model Context Protocol. It is marked Beta, so the setup and the list of actions may still change. For an agency, that means an assistant can take over small, repeated steps, such as finding a file or creating a share link, while the list of actions stays short and fixed.
Which assistants can connect
Claude Code, Codex, Cursor, VS Code (GitHub Copilot) and Windsurf each have setup steps for a token in Tarkle's client guides. Tarkle is still verifying each client end to end, so read the page for your assistant before you plan around it. Tarkle's Cursor and other MCP clients page covers Cursor, VS Code Copilot, Windsurf and any other MCP client. Claude on the web or desktop and ChatGPT custom connectors cannot connect with a token yet, because they need browser sign-in.
The connection that works today is a personal access token. You create it on the Claude & Codex page: you give it a name, choose an expiry of 30 days, 90 days or 1 year (90 days is the default), and copy it once, because it is not shown again. You then paste it into your assistant's settings. Browser sign-in is being rolled out client by client, so do not count on it yet.
MCP server file sharing AI agents: what they can and cannot do
Based on how the beta is built today, an assistant connected to Tarkle can:
list your workspaces and the files in them, with search
upload a file
create a share link for up to 25 files
create a file request link and list your file requests
see the files people submitted to a file request
It cannot delete files, download or read what is inside a file, change workspace or account settings, manage team members or roles, read billing, send email, or set a password on a link. That list is short on purpose, and it is the first thing to compare with what you actually want the assistant to do.
Two details matter for client work. The share links the assistant creates are public: anyone with the link can view and download, and no email is sent. And the token acts as the account that created it, with that account's permissions and your plan's storage limits, across every workspace the account belongs to. There is no read-only token and no token limited to one workspace yet.
Tasks that suit an MCP connection
The best tasks are repetitive and low risk:
finding a file by name when you cannot remember the folder
uploading a finished export and creating the share link in one prompt
creating a file request for a client and getting the link back
checking which requests are still waiting for files
An upload runs in steps behind the scenes: the assistant starts it, sends the file in parts, then checks until every byte has arrived. An assistant can only upload files it can reach. For a file it cannot reach, such as a chat attachment, it can get a browser upload link instead.
Tasks that do not suit it, because the tools do not exist: tidying or deleting old files, reading a contract to summarize it, or changing who has access to a workspace. Do those yourself.
Write down the three tasks you want from the assistant before you create a token. If an action is not on your list, you have just found what to keep out of reach.
Safety checklist before you connect
1. Give the least access you can
Because a token acts as the account that creates it, do not create it from the owner account. Invite a team member with a limited role, and create the token there. Tarkle's team roles are Owner, Admin, Member and Viewer. Listing files and creating share links need the role's permission to upload or share files. File requests are different: creating and listing them need only membership in the workspace, so a limited role does not stop an assistant from making them. The token also reaches every workspace that account belongs to, so check what each role can do before you rely on one.
Pick a short expiry too. A 30-day token for a pilot is easier to defend than a 1-year token nobody remembers.
2. Test with sample files
Make a test workspace with dummy files and a made-up client name. Ideally the account that owns the token belongs only to that workspace, since the token covers every workspace the account can reach. Ask the assistant to list the workspaces first. If you see client workspaces in the answer, stop and fix the account before going further.
Then run your three tasks. Open any share link the assistant created in a private window and look at what a stranger would see.
3. Review activity
Open the activity log, a searchable record of what happened across your workspace, with export. Its actor types are owner, member, guest and recipient, with no label for an AI assistant, so an action from a token may show under the account that created it. Do your test tasks, then check what appears. Do not assume every action is recorded until you have seen it for yourself. If you cannot see an action you need to see, keep the connection to test files only until you can.
4. Remove access when you finish
Revoke the token on the Claude & Codex page when the pilot ends, and again whenever someone leaves the team or you change assistants. Revoking a token stops the assistant from making new calls with it. It does not change the share links the token already created, so look at those in your workspace before you close the pilot.
Common mistakes
Creating the token from the owner account because it is quicker.
Testing with real client files "just once".
Forgetting that an assistant-made share link is public.
Leaving old tokens active after a pilot. A user can have up to 10 active tokens. The token list on the Claude & Codex page shows each token's name, last four characters, expiry and last-used date, so you can find an old one. An old token is still a key.
Assuming the assistant can read file contents. In this beta it cannot.
Next step
Pick one low-risk task, run it on sample files, and check the log. If you do not have a workspace yet, you can start for free and read the MCP server page for the latest status. For the human side of the same problem, see how to share files with clients without Google Drive.
What to remember about Tarkle
Tarkle's MCP server is in Beta. It lets an AI assistant list files, upload, create a public share link for up to 25 files and create file requests. Create the token from a limited team role, test on sample files, and revoke the token when the pilot ends. Start for free and read the MCP server page for the latest status.