YouTrack

Getting a token

1. In YouTrack open your profile → Account Security → Authentication → New token, give it the YouTrack scope, and copy it. Permanent tokens begin with perm:.
2. Set YOUTRACK_URL to your instance root. On YouTrack Cloud that is https://example.youtrack.cloud; on a self-hosted server it may include a context path such as https://yt.example.com/youtrack. No trailing slash. The adapter appends /api.
3. Set YOUTRACK_TOKEN. It is sent as Authorization: Bearer perm:….

fields is mandatory, and this is the thing to understand about YouTrack's API. Without it, YouTrack returns only $type and id for every object — technically a success, practically useless. The syntax is a nested selector: id,idReadable,summary,customFields(name,value(name)). Every tool below sends a useful default; override it when you need something else.

The query language is the powerful part. project: PROJ #Unresolved assignee: me sort by: updated desc is a complete query. It also handles created: {This week}, State: {In Progress}, #Bug, has: -attachments. This is the same grammar as the search box in the web UI, so anything a user can type there works here.

Custom fields are a nested array, not top-level properties. State, priority and assignee all live in customFields as {name, value:{name}} pairs. An agent looking for a top-level state property will not find one.

$skip and $top page, and there is no total count — a short page means the end.

Self-hosted, which is the thing to plan for.

• On AnythingMCP Cloud the instance must be reachable from the public internet on a real hostname with a valid TLS certificate. A self-signed certificate will fail: the connector offers no trust-anything switch.
• On an internal host (yt.intern, 10.0.0.x), self-host AnythingMCP on the same network and add that host to SSRF_ALLOWED_HOSTS, or the outbound guard refuses the call before it is made.

Writes: youtrack_add_comment posts a real comment that notifies the issue's watchers.