Tarkle connects to the tools your team already uses.
Partly available in the API.
API coverage
| What | Status | Where |
|---|---|---|
| MCP server for AI assistants | Available | MCP server |
| Agent guides and skill files | Available | AI agents |
| OpenAPI file | Available | API overview |
| Webhooks | Available for brand events | Webhooks |
| SDKs and a command line tool | Not available | Not in the API yet |
Setup for Slack is in the help center.
Access
The API and the MCP server use one credential, the API key. Only an owner or admin of the organization can make one. Open Settings > API, on the API keys tab, and choose Create. Enter a Name, then choose an Access: All workspaces, or Only selected workspaces with the workspaces ticked. A key does not expire. To stop a key at once, open its row menu and choose Delete.
Send the key on every request as a bearer token. Replace <your-tarkle-key> with the key you copied:
Authorization: Bearer <your-tarkle-key>A key starts with tk_. Tarkle shows the whole key once, when it is created. An owner or admin can copy it again from the row menu with Copy token. Rename is in the same menu.
Every call that works inside a workspace also names it with the eight-character workspace key, sent in the X-Workspace-Key header. The authentication page lists the errors for a missing or wrong workspace key.
What a key can do
A key can do everything the API and the MCP server can do, read and write, in every workspace it reaches. It acts as the person who made it, with that person’s role in each workspace. Brand endpoints also need that person to be an owner or admin of the workspace. A key cannot make purchases.
A key limited to selected workspaces gets 403 with the code no_access for any other workspace. Such a key also cannot create a workspace through the MCP server.
Keys made earlier keep working, within the permissions they hold. Some show a Legacy badge. Those keys hold fewer permissions, and they do not open the MCP server. Create a new key to get the full set.
MCP server
ChatGPT, Claude and Grok connect to the MCP server by browser sign-in, with no key. Coding assistants and other clients that take a header use the API key as Authorization: Bearer <your-tarkle-key> on https://mcp.tarkle.com/mcp. MCP tokens can no longer be created. The MCP server page has the setup for each assistant.
Related
- Start with the Quickstart
- Authentication: workspace keys, scopes and errors.
- Help center: how to use this in the app.
- Not in the API yet: the areas without endpoints.