--- title: "MCP server examples" description: "Ready prompts for an AI assistant on the Tarkle MCP server, the tools each one calls, and which steps ask you to confirm first." --- > Documentation Index > Fetch the complete documentation index at: https://tarkle.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # MCP server examples Each example is a prompt you can give an AI assistant that is connected to the Tarkle MCP server. Under each prompt, the steps name the tools the assistant calls, in the order it usually uses them, and mark the steps that ask you to confirm first. The assistant chooses its own calls, so read the steps as what happens, not as a script. Setup is on the [MCP server](/docs/mcp) page, and every tool is described on the [tools reference](/docs/mcp/tools) page. ## Before you start The assistant acts as the person who made the key, or as the person who signed in through the browser. It sees the workspaces that person can reach, and every tool runs as that person. The steps below that change brand pages, brand domains, team folders or members need the Owner or Admin role in that workspace. A key limited to selected workspaces reaches only those workspaces. A call that names another workspace is refused with "Workspace not found.", and a key limited this way cannot create a workspace. An older key that does not hold the full set of access cannot be used with the MCP server. If an assistant is refused with an older key, create a new key in Settings, API, as described on [API keys](/docs/get-started/api-keys). ## How confirmation works Some tools publish something, email someone or create a public link. The first call to one of these tools changes nothing. It describes what would happen and returns a confirmation code, and the assistant asks you whether to go ahead. Only after you say yes does it call the same tool again with the same inputs and that code. A code works only for the exact inputs it was made for, so if a title, a file or a role changes, the assistant asks again. These tools ask first: - `tarkle_create_transfer`, `tarkle_create_file_request`, `tarkle_reopen_file_request` and `tarkle_delete_file_request`. - `tarkle_set_portal_access` when it turns portal access on, and `tarkle_resend_portal_invite`. - `tarkle_invite_member`, `tarkle_change_member_role` and `tarkle_remove_member`. - `tarkle_update_brand` when it publishes a brand page, and `tarkle_create_workspace`. The steps below mark these with "It asks first." ## Share files with a client > Find the signed proposal and the three photos from the Northwind shoot in my Clients workspace, and make one public link for them titled "Northwind proposal and photos". 1. `tarkle_list_workspaces` finds the workspace where the person can share files. 2. `tarkle_list_files` finds the files by name and returns the fileId of each one. 3. `tarkle_create_transfer` makes a public link for up to 25 files. It asks first. Anyone with the link can view and download the files. Tarkle sends no email, so you send the link yourself. ## Collect files with a file request > Create a file request called "Q3 invoices" in my main workspace, saved in the Finance folder, with an expiry date of 30 November 2026. Then give me the link to send. 1. `tarkle_list_workspaces` finds the workspace. 2. `tarkle_list_folders` finds the Finance folder and returns its folderId. 3. `tarkle_create_file_request` creates the request with a public upload link. It asks first. Tarkle sends no email, so you send the link yourself. > How many files have people sent to "Q3 invoices" so far? Show me the names. 1. `tarkle_list_file_requests` finds the request and its requestId. 2. `tarkle_get_file_request_submissions` lists the files submitted to it. > Close the "Q3 invoices" request so it stops accepting uploads. 1. `tarkle_close_file_request` stops the link from accepting uploads. Files already submitted stay. It does not ask first. Reopening the request with `tarkle_reopen_file_request` asks first. ## Organise the library > In my Clients workspace, create a folder called Northwind with a Photos folder inside it. Save the brief I just pasted as brief.md in Northwind. 1. `tarkle_list_folders` lists the folders at the root. A name that is already used in a folder is refused, so the assistant reuses a folder that exists. 2. `tarkle_create_folder` creates Northwind and returns its folderId. A second call with that folderId as parentFolderId creates Photos inside it. 3. `tarkle_upload_text` saves the text as brief.md in the folder with that folderId. It takes up to 3 MB of text. > Save the report at https://example.com/q3-report.pdf in the Reports folder. 1. `tarkle_list_folders` finds the Reports folder. 2. `tarkle_upload_from_url` has Tarkle download the file and save it in that folder. The address must be reachable without a sign-in, and the file can be up to 50 MB. For bigger files the assistant uses `tarkle_get_upload_page`, or the steps on the [uploads](/docs/mcp/uploads) page. > Show me the files in Reports, newest first. 1. `tarkle_list_files` with the folderId lists the files directly in that folder, newest first. ## Build and update a brand page > Look up acme.com and tell me what you found and what is missing. Then create the Acme brand page in my Clients workspace as a draft and add their logo. 1. `tarkle_list_brands` lists the brand pages in the workspace. 2. `tarkle_lookup_brand_domain` searches the public web for the company and returns what it found: name, summary, colors, fonts, social links and image addresses, plus a list of what is missing. It saves nothing. 3. `tarkle_create_brand` creates the brand page from its name, summary and industry, which are required. The new page is always a private draft that nobody else can open. It does not ask first. 4. `tarkle_import_brand_file` fetches the logo from its public address and sets it as the main logo. > Connect brand.acme.com to the Acme brand page and tell me the DNS records to add. 1. `tarkle_connect_brand_domain` sets the domain and returns the DNS records and the steps. Tarkle does not change DNS itself. If the assistant has a tool for your DNS host, it can add the records. If not, you add them. 2. `tarkle_check_brand_domain` checks the setup again. Call it every 30 seconds after the records are added. The domain is live when its status is active. DNS changes usually show within minutes, and some hosts take up to 48 hours. > Publish the Acme brand page so anyone with the link can open it. 1. `tarkle_update_brand` with access set to public publishes the page. It asks first. Anyone with the link can open it, and any password on it is removed. ## Manage client portal contacts > Add Ana Ruiz (ana@northwind.example) from Northwind as a contact, give her client portal access, and set her upload limit to 20 GB. 1. `tarkle_create_contact` creates the contact and the Northwind organization, or reuses it, with Ana as its owner. Only the record is created: no email is sent and no login is made. Organizations are a Pro feature. 2. `tarkle_set_portal_access` turns portal access on. It asks first. The first time, Tarkle emails Ana an invite to sign in. The client portal is a Pro feature. 3. `tarkle_set_portal_storage_limit` sets her upload limit to 20 GB. No email is sent. The default is 5 GB. > Send Ana her sign-in link again. 1. `tarkle_list_contacts` finds her contactId, with a search by name, and shows whether her portal access is on. 2. `tarkle_resend_portal_invite` emails her the sign-in link again. It asks first. It fails when portal access is off. > Turn off Ana's client portal. 1. `tarkle_set_portal_access` with enabled set to false turns it off. It sends nothing and takes effect at once. ## Set up team folders > List my team folders with their budgets and how much each one uses. 1. `tarkle_list_team_folders` lists them, with the budget, the amount used and who can open each one. > Create a team folder called Design with a 50 GB budget that only the people I add can open, and give Sam access. 1. `tarkle_list_members` finds Sam's userId. 2. `tarkle_create_team_folder` creates Design. It is members only unless you choose everyone, and budgetGb sets the budget. Only workspace Owners and Admins can create one. Team folders are a Pro feature. No email is sent. 3. `tarkle_add_member_to_team_folder` gives Sam access. Sam must already be a workspace member. No email is sent. > Remove Sam's access to Design and take the storage limit off Design. 1. `tarkle_remove_member_from_team_folder` takes Sam's access away. Sam stays in the workspace and keeps the workspace role. Files in the folder stay. 2. `tarkle_set_team_folder_budget` with unlimited set to true removes the limit. The folder's people are not changed. ## Manage members > Invite jo@northwind.example to my workspace as a Viewer. 1. `tarkle_invite_member` emails them an invitation link as a Viewer. It asks first. > Change Sam's role to Member. 1. `tarkle_list_members` finds Sam's userId and role. 2. `tarkle_change_member_role` sets the role to Member. It asks first. > Remove jo from the workspace and hand what she added to me. 1. `tarkle_list_members` finds her userId and yours. 2. `tarkle_remove_member` removes her from the workspace, with your userId as transferToUserId. It asks first. They lose access at once, and the content they added goes to the person you name. Their Tarkle account is not deleted. ## When a tool refuses a step A refused call returns an error with a code and a short message, for example NOT_FOUND or FORBIDDEN. The [troubleshooting](/docs/mcp/troubleshooting) page covers the messages you are most likely to see. ## Related - [Tools reference](/docs/mcp/tools) - [Authorization and security](/docs/mcp/authorization) - [Uploads and file size](/docs/mcp/uploads) - [API keys](/docs/get-started/api-keys) Source: https://tarkle.com/docs/mcp/examples/index.mdx