Skip to content
Tarkle Docs

MCP server

Connect AI assistants to Tarkle through the MCP server, see what they can do, and find the setup, tools and security pages.

The Tarkle MCP server lets an AI assistant work with your Tarkle workspaces in plain words. You ask the assistant to send a file, collect files, build a brand page, add a contact or set up a team folder, and it does the work in Tarkle as the person who connected it. This page explains what the server does and how the pieces fit together. Setup for each assistant, the tools, and the rules are on the pages listed at the end.

What an assistant can do

The server offers 40 tools. They cover these areas:

  • Files and uploads. List files and folders, create a folder, and save text or a file from a public https address into a workspace.
  • Sharing and file requests. Create a public share link for files, audio or video, and create a file request with a public link that collects files from anyone who opens it.
  • Brand pages. List and read brand pages, look up a company by its website, create a brand page as a private draft, update it, and connect its custom domain.
  • Contacts and client portal. List and create contacts, turn a contact’s client portal on or off, and set how much a contact may upload.
  • Team folders and members. Create team folders, set their storage budgets, give a member access to a members-only team folder, and list, invite, change the role of or remove workspace members.

The tools reference lists every tool with what it does.

How it works in three steps

  1. Connect. Add the server address https://mcp.tarkle.com/mcp to your assistant, as a custom connector or as a remote MCP server.
  2. Sign in or send a key. ChatGPT, Claude and Grok sign in to Tarkle in the browser and approve access when asked. Coding assistants and other clients send your API key in an Authorization header: Authorization: Bearer <your-tarkle-key>.
  3. Ask. Start with a simple question such as “List my Tarkle workspaces.” A list of workspaces means the connection works.

Which assistants are documented

ChatGPT, Claude and Grok connect with browser sign-in and need no key. They are added as custom connectors with the server address. Claude Code, Codex, Cursor, VS Code (GitHub Copilot) and Windsurf connect with an API key. Any other client that supports remote MCP servers (streamable HTTP) with custom headers can connect the same way, with the key in the Authorization header.

Each assistant has its own setup steps: connect to chat assistants and connect to coding assistants.

What an assistant can see and do

An assistant acts as the person who connected it. It sees the workspaces that person can open, and it can do what that person’s role allows in each one. Browser sign-in covers every workspace the person can open. An API key acts as the person who created it, with that person’s access.

A key has one of two access choices, set when it is made:

  • All workspaces. The key reaches every workspace of the organization that its creator can open.
  • Only selected workspaces. The key reaches only the workspaces chosen. The assistant does not list the other workspaces, a tool call on another workspace returns Workspace not found, and the key cannot create a workspace.

Some tools change what other people see or receive: a public link, a file request with a public upload link, publishing a brand page, a client portal invite, a change to a member, or a new workspace. These ask first. The first call changes nothing and describes what would happen. The assistant shows it to you, and only after you say yes does it repeat the call with a confirmation code. The code works for those exact inputs only.

What is not available through MCP

The server does not have tools for these, so an assistant cannot do them:

  • Archiving, restoring or deleting a brand page, and removing a brand file.
  • Billing and purchases. No API key carries the purchase permission.
  • Deleting files, deleting a workspace, uploading a new version of a file, and editing a text file.

To manage brand pages from your own code, use the Brand API.

API keys for the server

Owners and admins of an organization create and manage keys in Settings, then API. A key has a name and an access choice, as described above. It has full read and write access to Tarkle for the workspaces it reaches, except purchases. The key is shown when it is made, and an owner or admin can copy it again later from the key’s menu with Copy token. The same menu renames and deletes it. A deleted key stops working at once.

A key marked Legacy was made before keys had full access, and the MCP server does not accept it. Create a new key for the assistant. MCP tokens can no longer be created, so new connections use a key or browser sign-in. The full key reference is on API keys.

Server address and agent guide

The server address is https://mcp.tarkle.com/mcp. The machine-readable setup guide for agents is at https://tarkle.com/install.md.

Pages in this section

Tarkle Docs

Type to search…

↑↓ navigate↵ selectEsc close