> ## Documentation Index
> Fetch the complete documentation index at: https://docs.utmkit.co/llms.txt
> Use this file to discover all available pages before exploring further.

# APIs & MCP

> Two doors into the same workspace: a REST API for your code, and an MCP server for your assistant.

Everything the console does to links, campaigns, rules and reports, a program can do too.
There are two ways in, and they open onto the same rooms: the same rules apply, the same
refusals come back in the same words, and every change is recorded in the
[activity log](/en/workspaces/activity-log) with the token that made it.

## The API

A REST API at `https://app.utmkit.co/api/v1`. Use it from a script, a backend, a
spreadsheet integration, or anything that can send an HTTP request. Every request carries a
token you mint on the console's tokens page; the token decides which workspace the request
acts on, so no request ever names one. Start with [Authentication & tokens](/en/developers/authentication),
then the reference in the sidebar: one page per operation, generated from the API's own
contract, with a playground to try a call from the browser.

## The MCP server

An MCP (Model Context Protocol) server at `https://app.utmkit.co/mcp`. Point Claude Desktop,
Claude Code, Cursor or any MCP client at it with the same kind of token, and your assistant
can list, create, edit and withdraw links, manage campaigns and rules, and read the report,
in your own words. Every tool maps to one token permission; a tool your token lacks is not
even shown. The [MCP server](/en/developers/mcp) page has the connection steps, and it
explains the one thing that trips people up: this site has an MCP server of its own, which
only searches these pages.

## Which one, when

* **A script or a backend** that creates links in bulk, syncs campaigns, or pulls the report
  into a dashboard: the API.
* **A person working through an assistant**, asking for "a link for the spring newsletter,
  source newsletter, medium email": the MCP server.
* **Your own server reporting a sale or a sign-up** against a link: the API, and only the
  API. A conversion is your server's event, not a person's, so it has no console form and
  no MCP tool. See [Conversions](/en/analytics/conversions).

## What both share

* **The token's permissions**, chosen when you mint it, and your role in the workspace,
  checked live on every call.
* **The workspace's rules**: a link that the convention, the approved values or the
  dependency rules would refuse in the console is refused here too, with the same sentence.
* **The rate limit**, per token, described in [Rate limits](/en/developers/rate-limits).
* **The error shape**, described in [Errors](/en/developers/errors).

## For assistants reading this site

This documentation is also published for machines. The page index is at
`https://docs.utmkit.co/llms.txt`, and every page has a plain-text twin: add `.md` to its
address. The MCP server at `https://docs.utmkit.co/mcp` searches these pages and nothing
else; it does not touch your workspace. To operate a workspace, use the product's server
described on the [MCP server](/en/developers/mcp) page.