@vitalyostanin/youtrack-mcp 0.7.0 → 0.7.1

package/README-ru.md

@@ -53,6 +53,7 @@ MCP сервер для полноценной интеграции с YouTrack
   - `YOUTRACK_HOLIDAYS` — опциональный список праздничных дат через запятую (формат `YYYY-MM-DD`), исключаемых из отчётов и массовых операций
   - `YOUTRACK_PRE_HOLIDAYS` — опциональный список предпраздничных дат через запятую, для которых норма времени уменьшается автоматически
   - `YOUTRACK_USER_ALIASES` — опциональный список соответствий `alias:login` через запятую (например, `me:vyt,petya:p.petrov`), используется при автоматическом выборе исполнителей
+  - `YOUTRACK_DEFAULT_PROJECT` — опциональный код проекта (shortName или ID), используемый по умолчанию при создании задач/статей и для преобразования коротких идентификаторов (например, `1234` → `PROJ-1234`)
   - `YOUTRACK_USE_STRUCTURED_CONTENT` — опциональный, управляет форматом ответа (по умолчанию: `true`). При `true` инструменты возвращают только узел MCP `structuredContent` с полными данными. При `false` инструменты возвращают только узел MCP `content` (один текстовый элемент с JSON-строкой)
 
 ## Установка
@@ -64,6 +65,7 @@ MCP сервер для полноценной интеграции с YouTrack
 ```bash
 YOUTRACK_URL="https://youtrack.example.com" \
 YOUTRACK_TOKEN="perm:your-token-here" \
+YOUTRACK_DEFAULT_PROJECT="PROJ" \
 npx -y @vitalyostanin/youtrack-mcp@latest
 ```
 
@@ -281,7 +283,7 @@ YOUTRACK_TOKEN = "perm:your-token-here"
 | `issues_details` | Режимы краткий/полный для множества задач (макс 50). **Краткий:** предопределённые поля. **Полный (`briefOutput=false`):** добавляет `customFields` для каждой задачи. **Замечание:** объём ответа может быть большим, поэтому по умолчанию используется краткий режим. **Ограничение:** максимум 50 задач за запрос | `issueIds[]` — массив кодов задач; `briefOutput` — опционально (по умолчанию `true`) |
 | `issue_comments` | Комментарии задачи. **Использование:** Просмотр всех комментариев к задаче. **Возвращает:** предопределенные поля - id, text, textPreview, usesMarkdown, author (id, login, name), created, updated | `issueId` — код задачи |
 | `issues_comments` | Комментарии для нескольких задач (пакетный режим, макс 50). **Использование:** Эффективное получение комментариев для множества задач одновременно. **Ограничение:** максимум 50 задач за запрос | `issueIds[]` — массив кодов задач |
-| `issue_create` | Создание новой задачи в YouTrack. **Использование:** Создание задач, подзадач (через `parentIssueId`), назначение исполнителя при создании. **Возвращает:** стандартные поля созданной задачи (id, idReadable, summary, description, wikifiedDescription, usesMarkdown, project, parent, assignee). Пользовательские поля не включены. | `projectId` — ID проекта (внутренний YouTrack ID), `summary` — краткое описание задачи, опционально `description`, `parentIssueId`, `assigneeLogin` (логин или `me`), `usesMarkdown` |
+| `issue_create` | Создание новой задачи в YouTrack. **Использование:** Создание задач, подзадач (через `parentIssueId`), назначение исполнителя при создании, одновременное создание дополнительных связей. **Возвращает:** стандартные поля созданной задачи (id, idReadable, summary, description, wikifiedDescription, usesMarkdown, project, parent, assignee). Пользовательские поля не включены. | `projectId` — внутренний ID проекта, `summary`, опционально `description`, `parentIssueId`, `assigneeLogin`, `stateName`, `usesMarkdown`, `links[]` — массив объектов связи |
 | `issue_update` | Обновление существующей задачи. **Использование:** Изменение summary, description, родительской задачи. **Примечание:** для изменения исполнителя используйте `issue_assign`. Пустая строка в `parentIssueId` удаляет родителя. **Возвращает:** стандартные поля обновленной задачи | `issueId` — ID или код задачи, опционально `summary`, `description`, `parentIssueId` (пустая строка очищает родителя), `usesMarkdown` |
 | `issue_assign` | Назначение исполнителя для задачи. **Использование:** Изменение исполнителя задачи. Поддерживает алиас `me` для текущего пользователя. **Возвращает:** стандартные поля обновленной задачи | `issueId` — ID или код задачи, `assigneeLogin` — логин исполнителя или `me` |
 | `issue_comment_create` | Добавление комментария к задаче. **Использование:** Оставлять комментарии, заметки, обсуждения в задачах. Поддерживает Markdown. **Возвращает:** поля комментария - id, text, textPreview, usesMarkdown, author, created, updated | `issueId` — ID или код задачи, `text` — текст комментария, опционально `usesMarkdown` |
@@ -299,6 +301,16 @@ YOUTRACK_TOKEN = "perm:your-token-here"
 | `issue_link_add` | Создание связи между двумя задачами | `sourceId` — исходная задача, `targetId` — целевая задача, `linkType` — имя или id типа связи (например, `Relates` или UUID) |
 | `issue_link_delete` | Удаление существующей связи по её id для указанной задачи | `issueId` — код задачи, `linkId` — id связи |
 
+**issue_create — дополнительные параметры:**
+
+- `parentIssueId` — если указан только числовой идентификатор (`"123"`), автоматически добавляет префикс проекта по умолчанию (например, `BC-123`).
+- `links[]` — массив объектов для создания связей после сохранения задачи. Каждый объект поддерживает поля:
+  - `linkType` — имя или id типа связи (например, `Subtask`, `Relates`).
+  - `targetId` — idReadable задачи или числовой идентификатор, который также резолвится через проект по умолчанию.
+  - `direction` — опционально (`"outbound"` по умолчанию). Используйте `"inbound"`, чтобы инвертировать направление для несимметричных типов.
+  - `sourceId` — опционально. Если не указан, исходной считается новая задача; укажите его, чтобы привязать новую задачу как `target` к уже существующей.
+- После создания задачи повторно запросите связи (`issue_links`) для подтверждения, что YouTrack применил все отношения.
+
 ### Звездочки задач
 
 | Tool | Описание | Основные параметры |
@@ -346,6 +358,8 @@ YOUTRACK_TOKEN = "perm:your-token-here"
 | `article_create` | Создание статьи в базе знаний. **Использование:** Создание документации, инструкций, статей поддержки. Поддерживает иерархическую структуру через `parentArticleId`. **Возвращает:** предопределенные поля созданной статьи - id, idReadable, summary, content, contentPreview, usesMarkdown, parentArticle, project | `summary` — заголовок статьи, опционально `content` — содержимое, `parentArticleId` — ID родительской статьи для создания подстатьи, `projectId` — ID проекта, `usesMarkdown` — использовать Markdown форматирование, `returnRendered` — вернуть отрендеренный preview |
 | `article_update` | Обновление существующей статьи. **Использование:** Редактирование содержимого, изменение заголовка статьи. **Возвращает:** предопределенные поля обновленной статьи | `articleId` — ID статьи, опционально `summary` — новый заголовок, `content` — новое содержимое, `usesMarkdown`, `returnRendered` |
 | `article_search` | Поиск статей в базе знаний по тексту. **Использование:** Полнотекстовый поиск по заголовкам и содержимому статей, поиск документации. Поддерживает фильтрацию по проекту и родительской статье. **Возвращает:** предопределенные поля - id, idReadable, summary, usesMarkdown, contentPreview (если `returnRendered=true`), parentArticle, project. Поле content не включено для производительности. **Ограничение:** минимум 2 символа в запросе, максимум 200 результатов | `query` — текст для поиска (минимум 2 символа), опционально `projectId` — фильтр по проекту, `parentArticleId` — фильтр по родительской статье, `limit` — максимум результатов (макс 200), `returnRendered` — вернуть отрендеренный preview содержимого |
+| `issues_list` | Список задач по фильтрам с поддержкой сортировки. **Использование:** Дашборды, аудит командной загрузки, подготовка батч-операций. Поддерживает фильтрацию по проектам, датам создания/обновления, статусам, типам, исполнителю. **Возвращает:** краткие или полные данные задачи в зависимости от `briefOutput`, а также информацию о сортировке и пагинации. | Фильтры: `projectIds`, `createdAfter/Before`, `updatedAfter/Before`, `statuses`, `assigneeLogin`, `types`; сортировка: `sortField` (`created`/`updated`), `sortDirection` (`asc`/`desc`); пагинация: `limit`, `skip`; формат: `briefOutput` |
+| `issues_count` | Подсчёт задач с теми же фильтрами, что у `issues_list`, с разбивкой по проектам. **Использование:** Быстрая оценка объёмов работ перед загрузкой полного списка, подготовка аналитических отчётов. При запросе одного проекта обращается к `/api/issuesGetter/count`, иначе считает постранично. | Те же фильтры, что и `issues_list`; опциональный `top` ограничивает объём ручной агрегации (при необходимости частичной выборки) |
 
 ### Вложения
 

package/README.md

@@ -55,9 +55,10 @@ MCP server for comprehensive YouTrack integration with the following capabilitie
   - `YOUTRACK_TOKEN` — permanent token with read permissions for issues and work items
   - `YOUTRACK_TIMEZONE` — optional timezone for date operations (default: `Europe/Moscow`), must be a valid IANA timezone identifier (e.g., `Europe/London`, `America/New_York`, `Asia/Tokyo`)
   - `YOUTRACK_HOLIDAYS` — optional comma-separated list of holiday dates (format `YYYY-MM-DD`), excluded from reports and batch operations
-  - `YOUTRACK_PRE_HOLIDAYS` — optional comma-separated list of pre-holiday dates with reduced working hours
-  - `YOUTRACK_USER_ALIASES` — optional comma-separated list of `alias:login` mappings (e.g., `me:vyt,petya:p.petrov`), used for automatic assignee selection
-  - `YOUTRACK_USE_STRUCTURED_CONTENT` — optional, controls response format (default: `true`). When `true`, tools return only the MCP `structuredContent` node with full data. When `false`, tools return only the MCP `content` node (single text item with JSON string)
+- `YOUTRACK_PRE_HOLIDAYS` — optional comma-separated list of pre-holiday dates with reduced working hours
+- `YOUTRACK_USER_ALIASES` — optional comma-separated list of `alias:login` mappings (e.g., `me:vyt,petya:p.petrov`), used for automatic assignee selection
+- `YOUTRACK_DEFAULT_PROJECT` — optional project code used for manual verification tasks and default parent issues in docs/examples (use `PROJ` in documentation examples)
+- `YOUTRACK_USE_STRUCTURED_CONTENT` — optional, controls response format (default: `true`). When `true`, tools return only the MCP `structuredContent` node with full data. When `false`, tools return only the MCP `content` node (single text item with JSON string)
 
 ## Installation
 
@@ -68,6 +69,7 @@ You can run the server directly with npx without installation:
 ```bash
 YOUTRACK_URL="https://youtrack.example.com" \
 YOUTRACK_TOKEN="perm:your-token-here" \
+YOUTRACK_DEFAULT_PROJECT="PROJ" \
 npx -y @vitalyostanin/youtrack-mcp@latest
 ```
 
@@ -282,7 +284,7 @@ Tools return either `structuredContent` (default) or a text `content` item, depe
 | `issue_lookup` | Brief issue information | `issueId` — issue code (e.g., PROJ-123) |
 | `issue_details` | Issue details with brief/full modes | `issueId` — issue code; `briefOutput` — optional boolean (default `true`). Brief: predefined fields only. Full (`false`): adds `customFields` including `State` |
 | `issue_comments` | Issue comments | `issueId` — issue code |
-| `issue_create` | Create issue | `projectId`, `summary`, optionally `description`, `parentIssueId`, `assigneeLogin`, `usesMarkdown` |
+| `issue_create` | Create issue | `projectId`, `summary`, optional `description`, `parentIssueId`, `assigneeLogin`, `stateName`, `usesMarkdown`, `links` (array of link objects) |
 | `issue_update` | Update existing issue | `issueId`, optionally `summary`, `description`, `parentIssueId` (empty string clears parent), `usesMarkdown` |
 | `issue_assign` | Assign issue to user | `issueId`, `assigneeLogin` (login or `me`) |
 | `issue_comment_create` | Add comment to issue | `issueId`, `text` — comment text, optionally `usesMarkdown` |
@@ -358,6 +360,8 @@ Tools return either `structuredContent` (default) or a text `content` item, depe
 | Tool | Description | Main Parameters |
 | --- | --- | --- |
 | `article_search` | Search articles in knowledge base | `query`, optionally `projectId`, `parentArticleId`, `limit`, `returnRendered` |
+| `issues_list` | List issues across projects with filtering and sorting | Filters: `projectIds`, `createdAfter/Before`, `updatedAfter/Before`, `statuses`, `assigneeLogin`, `types`; Sorting: `sortField`, `sortDirection`; Pagination: `limit`, `skip`; Output mode: `briefOutput` |
+| `issues_count` | Count issues using same filters as `issues_list`, returns per-project breakdown | Same filters as above, optional `top` to cap manual aggregation when many projects are involved |
 
 ## Important Notes
 
@@ -366,3 +370,12 @@ Tools return either `structuredContent` (default) or a text `content` item, depe
 Some operations cannot be undone and require explicit confirmation:
 
 - **`issue_attachment_delete`** - Requires `confirmation: true` parameter. Deleted attachments cannot be recovered.
+**issue_create parameters:**
+
+- `parentIssueId` — resolves against `YOUTRACK_DEFAULT_PROJECT` when no project prefix is provided (e.g., `123` → `BC-123` if default project is `BC`).
+- `links[]` — optional array describing additional links to create after the issue is saved. Each item supports:
+  - `linkType` — name or id of the link type (e.g., `Subtask`, `Relates`).
+  - `targetId` — issue id or readable id. Plain numbers are resolved with the default project, matching `resolveIssueId` behaviour.
+  - `direction` — optional (`"outbound"` by default). Use `"inbound"` to flip direction for non-symmetric link types.
+  - `sourceId` — optional. When omitted, the new issue is treated as the source. Specify to create links from an existing issue to the new one (useful for complex chains).
+- After creation the tool automatically refreshes the issue and attempts to reopen link caches; always re-fetch links with `issue_links` to confirm the final state.

package/dist/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@vitalyostanin/youtrack-mcp",
-    "version": "0.7.0",
+    "version": "0.7.1",
     "scripts": {
         "build": "tsc -p tsconfig.json",
         "postbuild": "chmod +x dist/index.js",

package/dist/src/config.js

@@ -6,6 +6,7 @@ const configSchema = z.object({
     YOUTRACK_HOLIDAYS: z.string().optional(),
     YOUTRACK_PRE_HOLIDAYS: z.string().optional(),
     YOUTRACK_USER_ALIASES: z.string().optional(),
+    YOUTRACK_DEFAULT_PROJECT: z.string().optional(),
     YOUTRACK_USE_STRUCTURED_CONTENT: z
         .string()
         .optional()
@@ -37,6 +38,7 @@ export function loadConfig(env = process.env) {
         userAliases: parsed.data.YOUTRACK_USER_ALIASES
             ? parseAliasMap(parsed.data.YOUTRACK_USER_ALIASES)
             : undefined,
+        defaultProject: parsed.data.YOUTRACK_DEFAULT_PROJECT,
         useStructuredContent: parsed.data.YOUTRACK_USE_STRUCTURED_CONTENT,
     };
 }

package/dist/src/tools/article-tools.js

@@ -5,7 +5,10 @@ const articleLookupArgs = {
 };
 const articleListArgs = {
     parentArticleId: z.string().optional().describe("Parent article ID"),
-    projectId: z.string().optional().describe("Project ID"),
+    projectId: z
+        .string()
+        .optional()
+        .describe("Project ID (defaults to YOUTRACK_DEFAULT_PROJECT when omitted)"),
 };
 const articleCreateArgs = {
     summary: z.string().min(1).describe("Article title"),
@@ -14,7 +17,10 @@ const articleCreateArgs = {
         .optional()
         .describe("Article content. Supports folded sections: <details> <summary>Title</summary>Content</details>"),
     parentArticleId: z.string().optional().describe("Parent article ID"),
-    projectId: z.string().optional().describe("Project ID"),
+    projectId: z
+        .string()
+        .optional()
+        .describe("Project ID (defaults to YOUTRACK_DEFAULT_PROJECT when omitted)"),
     usesMarkdown: z.boolean().optional().describe("Use Markdown formatting"),
     returnRendered: z.boolean().optional().describe("Return rendered content preview"),
 };
@@ -60,7 +66,7 @@ export function registerArticleTools(server, client) {
             return errorResponse;
         }
     });
-    server.tool("article_create", "Create article in YouTrack knowledge base. Supports markdown with folded sections (<details>/<summary>) in content. Note: Response includes predefined fields only - id, idReadable, summary, content, contentPreview, usesMarkdown, parentArticle (id, idReadable), project (id, shortName, name).", articleCreateArgs, async (rawInput) => {
+    server.tool("article_create", "Create article in YouTrack knowledge base. Supports markdown with folded sections (<details>/<summary>) in content. Note: Response includes predefined fields only - id, idReadable, summary, content, contentPreview, usesMarkdown, parentArticle (id, idReadable), project (id, shortName, name). After creation, fetch the article again to confirm rendered content and hierarchy are correct.", articleCreateArgs, async (rawInput) => {
         try {
             const payload = articleCreateSchema.parse(rawInput);
             const article = await client.createArticle({
@@ -79,7 +85,7 @@ export function registerArticleTools(server, client) {
             return errorResponse;
         }
     });
-    server.tool("article_update", "Update existing article. Supports markdown with folded sections (<details>/<summary>) in content. Note: Response includes predefined fields only - id, idReadable, summary, content, contentPreview, usesMarkdown, parentArticle (id, idReadable), project (id, shortName, name).", articleUpdateArgs, async (rawInput) => {
+    server.tool("article_update", "Update existing article. Supports markdown with folded sections (<details>/<summary>) in content. Note: Response includes predefined fields only - id, idReadable, summary, content, contentPreview, usesMarkdown, parentArticle (id, idReadable), project (id, shortName, name). After updating, re-fetch the article (optionally with rendered content) to verify formatting and links.", articleUpdateArgs, async (rawInput) => {
         try {
             const payload = articleUpdateSchema.parse(rawInput);
             if (payload.summary === undefined && payload.content === undefined) {

package/dist/src/tools/attachment-tools.js

@@ -64,7 +64,7 @@ export function registerAttachmentTools(server, client) {
             return errorResponse;
         }
     });
-    server.tool("issue_attachment_upload", "Upload one or more files to a YouTrack issue. Files must exist on the local filesystem. Note: Can only attach files to existing issues, not during issue creation.", attachmentUploadArgs, async (rawInput) => {
+    server.tool("issue_attachment_upload", "Upload one or more files to a YouTrack issue. Files must exist on the local filesystem. Note: Can only attach files to existing issues, not during issue creation. After uploading, fetch the attachments list to verify each file appears with correct metadata.", attachmentUploadArgs, async (rawInput) => {
         try {
             const payload = attachmentUploadSchema.parse(rawInput);
             const result = await client.uploadAttachments({
@@ -80,7 +80,7 @@ export function registerAttachmentTools(server, client) {
             return errorResponse;
         }
     });
-    server.tool("issue_attachment_delete", "Delete an attachment from a YouTrack issue. IMPORTANT: Requires explicit confirmation via the 'confirmation' parameter to prevent accidental deletion. This is a destructive operation that cannot be undone.", attachmentDeleteArgs, async (rawInput) => {
+    server.tool("issue_attachment_delete", "Delete an attachment from a YouTrack issue. IMPORTANT: Requires explicit confirmation via the 'confirmation' parameter to prevent accidental deletion. This is a destructive operation that cannot be undone. After deletion, list attachments again to ensure the file no longer appears.", attachmentDeleteArgs, async (rawInput) => {
         try {
             const payload = attachmentDeleteSchema.parse(rawInput);
             const result = await client.deleteAttachment({

package/dist/src/tools/issue-link-tools.js

@@ -11,13 +11,12 @@ const linkCreateArgs = {
         .string()
         .min(1)
         .describe("Link type name or id (e.g., 'Relates', 'Duplicate', or a type id)"),
+    direction: z
+        .enum(["inbound", "outbound"])
+        .optional()
+        .describe("Direction relative to the source issue (use 'inbound' to flip the relationship)"),
 };
 const linkCreateSchema = z.object(linkCreateArgs);
-const linkDeleteArgs = {
-    issueId: z.string().min(1).describe("Issue code that holds the link (e.g., PROJ-123)"),
-    linkId: z.string().min(1).describe("Issue link id (internal youtrack id)"),
-};
-const linkDeleteSchema = z.object(linkDeleteArgs);
 export function registerIssueLinkTools(server, client) {
     server.tool("issue_links", "List issue links for a given YouTrack issue. Use for: inspecting relationships like 'relates to', 'duplicates', 'parent/child'. Response includes link id, direction, linkType, and counterpart issue brief (idReadable, summary, project, assignee).", issueIdArgs, async (rawInput) => {
         try {
@@ -38,7 +37,7 @@ export function registerIssueLinkTools(server, client) {
             return toolError(error);
         }
     });
-    server.tool("issue_link_add", "Create a link between two issues. Provide sourceId, targetId and linkType (name or id). Limitations: link type must exist in project context; API may reject invalid combinations.", linkCreateArgs, async (rawInput) => {
+    server.tool("issue_link_add", "Create a link between two issues. Provide sourceId, targetId and linkType (name or id). Limitations: link type must exist in project context; API may reject invalid combinations. After linking, fetch the issue links again to confirm the relationship appears as expected.", linkCreateArgs, async (rawInput) => {
         try {
             const input = linkCreateSchema.parse(rawInput);
             const result = await client.addIssueLink(input);
@@ -48,15 +47,5 @@ export function registerIssueLinkTools(server, client) {
             return toolError(error);
         }
     });
-    server.tool("issue_link_delete", "Delete an existing issue link by id for a given issue. Use 'issue_links' to discover link ids first.", linkDeleteArgs, async (rawInput) => {
-        try {
-            const input = linkDeleteSchema.parse(rawInput);
-            const result = await client.deleteIssueLink(input);
-            return toolSuccess(result);
-        }
-        catch (error) {
-            return toolError(error);
-        }
-    });
 }
 //# sourceMappingURL=issue-link-tools.js.map

package/dist/src/tools/issue-search-tools.js

@@ -36,6 +36,108 @@ const issueSearchByUserActivityArgs = {
         .describe("Number of results to skip for pagination (default: 0)"),
 };
 const issueSearchByUserActivitySchema = z.object(issueSearchByUserActivityArgs);
+const issueListArgs = {
+    projectIds: z
+        .array(z.string().min(1))
+        .optional()
+        .describe("Filter by project IDs (e.g., ['0-0']). When omitted, returns issues from all projects."),
+    createdAfter: z
+        .string()
+        .optional()
+        .describe("Only include issues created on or after this date (YYYY-MM-DD or ISO timestamp)."),
+    createdBefore: z
+        .string()
+        .optional()
+        .describe("Only include issues created on or before this date (YYYY-MM-DD or ISO timestamp)."),
+    updatedAfter: z
+        .string()
+        .optional()
+        .describe("Only include issues updated on or after this date (YYYY-MM-DD or ISO timestamp)."),
+    updatedBefore: z
+        .string()
+        .optional()
+        .describe("Only include issues updated on or before this date (YYYY-MM-DD or ISO timestamp)."),
+    statuses: z
+        .array(z.string().min(1))
+        .optional()
+        .describe("Filter by workflow states (e.g., ['Open', 'In Progress'])."),
+    assigneeLogin: z
+        .string()
+        .optional()
+        .describe("Filter by assignee login (case-sensitive; use 'me' for current user)."),
+    types: z
+        .array(z.string().min(1))
+        .optional()
+        .describe("Filter by issue types (e.g., ['Bug', 'Feature'])."),
+    sortField: z
+        .enum(["created", "updated"])
+        .optional()
+        .describe("Sort by created or updated timestamp (default: created)."),
+    sortDirection: z
+        .enum(["asc", "desc"])
+        .optional()
+        .describe("Sort direction: 'asc' for oldest first, 'desc' for newest first (default)."),
+    briefOutput: z
+        .boolean()
+        .optional()
+        .describe("Return brief issue data without description fields (default: true). Set to false to include description and wikifiedDescription fields."),
+    limit: z
+        .number()
+        .int()
+        .positive()
+        .max(200)
+        .optional()
+        .describe("Maximum number of issues to return (default: 200, max: 200)."),
+    skip: z
+        .number()
+        .int()
+        .nonnegative()
+        .optional()
+        .describe("Number of issues to skip for pagination (default: 0)."),
+};
+const issueListSchema = z.object(issueListArgs);
+const issueCountArgs = {
+    projectIds: z
+        .array(z.string().min(1))
+        .optional()
+        .describe("Filter by project IDs (e.g., ['0-0']). When omitted, counts cover all projects."),
+    createdAfter: z
+        .string()
+        .optional()
+        .describe("Only include issues created on or after this date (YYYY-MM-DD or ISO timestamp)."),
+    createdBefore: z
+        .string()
+        .optional()
+        .describe("Only include issues created on or before this date (YYYY-MM-DD or ISO timestamp)."),
+    updatedAfter: z
+        .string()
+        .optional()
+        .describe("Only include issues updated on or after this date (YYYY-MM-DD or ISO timestamp)."),
+    updatedBefore: z
+        .string()
+        .optional()
+        .describe("Only include issues updated on or before this date (YYYY-MM-DD or ISO timestamp)."),
+    statuses: z
+        .array(z.string().min(1))
+        .optional()
+        .describe("Filter by workflow states (e.g., ['Open', 'In Progress'])."),
+    assigneeLogin: z
+        .string()
+        .optional()
+        .describe("Filter by assignee login (case-sensitive; use 'me' for current user)."),
+    types: z
+        .array(z.string().min(1))
+        .optional()
+        .describe("Filter by issue types (e.g., ['Bug', 'Feature'])."),
+    top: z
+        .number()
+        .int()
+        .positive()
+        .max(1000)
+        .optional()
+        .describe("Optional safety limit for manual aggregation when multiple projects are requested. When set, counting stops after processing this many issues, so totals may be partial."),
+};
+const issueCountSchema = z.object(issueCountArgs);
 export function registerIssueSearchTools(server, client) {
     server.tool("issue_search_by_user_activity", "Search for issues where specified users had activity (updated, mentioned, reported, assigned, commented) within a given time period. Supports two filter modes: 'issue_updated' (default, fast) uses issue.updated field, 'user_activity' (slow, precise) checks actual user activity dates including comments, mentions, and field changes history. Results are sorted by activity time (most recent first). When 'user_activity' mode is used, each issue includes 'lastActivityDate' field with exact timestamp of user's last activity. Supports pagination via limit and skip parameters. Note: By default (briefOutput=true), each issue includes minimal fields only - id, idReadable, summary, project (id, shortName, name), parent (id, idReadable), assignee (id, login, name). Description fields are excluded to reduce response size. Set briefOutput=false to include full description and wikifiedDescription fields. Custom fields are not included.", issueSearchByUserActivityArgs, async (rawInput) => {
         try {
@@ -57,5 +159,53 @@ export function registerIssueSearchTools(server, client) {
             return errorResponse;
         }
     });
+    server.tool("issues_list", "List issues across projects with rich filtering and configurable sorting. Use for: Building dashboards, auditing work across teams, feeding batch workflows. Supports filtering by project IDs, creation/update windows, workflow states, assignee login, and issue types. Sorting accepts created/updated fields with asc/desc direction so you can fetch newest or oldest pages first. Pagination is controlled with limit/skip (max 200 per call). Note: By default (briefOutput=true) returns minimal fields (id, idReadable, summary, project, parent, assignee, watchers.hasStar). Set briefOutput=false to include description and wikifiedDescription fields. After processing a page, re-fetch if you must verify that status or assignee changes did not occur in the meantime.", issueListArgs, async (rawInput) => {
+        try {
+            const payload = issueListSchema.parse(rawInput);
+            const results = await client.listIssues({
+                projectIds: payload.projectIds,
+                createdAfter: payload.createdAfter,
+                createdBefore: payload.createdBefore,
+                updatedAfter: payload.updatedAfter,
+                updatedBefore: payload.updatedBefore,
+                statuses: payload.statuses,
+                assigneeLogin: payload.assigneeLogin,
+                types: payload.types,
+                sortField: payload.sortField,
+                sortDirection: payload.sortDirection,
+                briefOutput: payload.briefOutput,
+                limit: payload.limit,
+                skip: payload.skip,
+            });
+            const response = toolSuccess(results);
+            return response;
+        }
+        catch (error) {
+            const errorResponse = toolError(error);
+            return errorResponse;
+        }
+    });
+    server.tool("issues_count", "Count issues across projects using the same filters as issues_list. Use for: Gauging workload distribution, preparing dashboards, validating automation scope before fetching full issue payloads. Returns total matches and per-project breakdown when multiple projects are involved. When only one project is filtered, delegates to YouTrack's /api/issuesGetter/count for an exact total; otherwise counts are aggregated client-side with pagination (default batches of 200, controlled by optional top limit for partial sampling). If you use a small top value, totals may be truncated — re-run without top to confirm final numbers.", issueCountArgs, async (rawInput) => {
+        try {
+            const payload = issueCountSchema.parse(rawInput);
+            const results = await client.countIssues({
+                projectIds: payload.projectIds,
+                createdAfter: payload.createdAfter,
+                createdBefore: payload.createdBefore,
+                updatedAfter: payload.updatedAfter,
+                updatedBefore: payload.updatedBefore,
+                statuses: payload.statuses,
+                assigneeLogin: payload.assigneeLogin,
+                types: payload.types,
+                top: payload.top,
+            });
+            const response = toolSuccess(results);
+            return response;
+        }
+        catch (error) {
+            const errorResponse = toolError(error);
+            return errorResponse;
+        }
+    });
 }
 //# sourceMappingURL=issue-search-tools.js.map

package/dist/src/tools/issue-star-tools.js

@@ -21,15 +21,15 @@ function createToolHandler(handler) {
  */
 export function registerIssueStarTools(server, client) {
     // Tool: issue_star
-    server.tool("issue_star", "Add star to YouTrack issue for current user. Use for: Marking important issues, Adding issues to watchlist, Quick access to frequently used issues. Returns: Confirmation of star status with issueId and starred flag. Note: If issue is already starred, returns success without making changes (idempotent operation).", {
+    server.tool("issue_star", "Add star to YouTrack issue for current user. Use for: Marking important issues, Adding issues to watchlist, Quick access to frequently used issues. Returns: Confirmation of star status with issueId and starred flag. Note: If issue is already starred, returns success without making changes (idempotent operation). After starring, fetch the issue or starred list again to confirm the flag is set.", {
         issueId: z.string().min(1).describe("Issue code (e.g., PROJ-123)"),
     }, createToolHandler(async (args) => client.starIssue(args.issueId)));
     // Tool: issue_unstar
-    server.tool("issue_unstar", "Remove star from YouTrack issue for current user. Use for: Removing issues from watchlist, Cleaning up unneeded stars, Managing starred issues list. Returns: Confirmation of unstar operation with issueId and starred flag. Note: If issue is not currently starred, returns success without making changes (idempotent operation).", {
+    server.tool("issue_unstar", "Remove star from YouTrack issue for current user. Use for: Removing issues from watchlist, Cleaning up unneeded stars, Managing starred issues list. Returns: Confirmation of unstar operation with issueId and starred flag. Note: If issue is not currently starred, returns success without making changes (idempotent operation). After unstarring, refresh the issue or starred list to ensure the star was cleared.", {
         issueId: z.string().min(1).describe("Issue code (e.g., PROJ-123)"),
     }, createToolHandler(async (args) => client.unstarIssue(args.issueId)));
     // Tool: issues_star_batch
-    server.tool("issues_star_batch", "Add stars to multiple YouTrack issues (batch mode, max 50 issues). Use for: Bulk marking important issues, Batch adding to watchlist, Processing multiple issues at once, Quick setup of starred issues list. Returns: Object with 'successful' array (starred issues) and 'failed' array (errors with issue IDs). Note: Operations are processed with concurrency limit (10 concurrent requests) to prevent API overload. Partial success is possible - some issues may succeed while others fail.", {
+    server.tool("issues_star_batch", "Add stars to multiple YouTrack issues (batch mode, max 50 issues). Use for: Bulk marking important issues, Batch adding to watchlist, Processing multiple issues at once, Quick setup of starred issues list. Returns: Object with 'successful' array (starred issues) and 'failed' array (errors with issue IDs). Note: Operations are processed with concurrency limit (10 concurrent requests) to prevent API overload. Partial success is possible - some issues may succeed while others fail. After completion, reload the starred list to confirm which issues were starred.", {
         issueIds: z
             .array(z.string().min(1))
             .min(1)
@@ -37,7 +37,7 @@ export function registerIssueStarTools(server, client) {
             .describe("Array of issue codes (e.g., ['PROJ-123', 'PROJ-124']), max 50"),
     }, createToolHandler(async (args) => client.starIssues(args.issueIds)));
     // Tool: issues_unstar_batch
-    server.tool("issues_unstar_batch", "Remove stars from multiple YouTrack issues (batch mode, max 50 issues). Use for: Bulk cleanup of watchlist, Batch removal of unneeded stars, Processing multiple issues at once, Managing starred issues list. Returns: Object with 'successful' array (unstarred issues) and 'failed' array (errors with issue IDs). Note: Operations are processed with concurrency limit (10 concurrent requests) to prevent API overload. Partial success is possible - some issues may succeed while others fail.", {
+    server.tool("issues_unstar_batch", "Remove stars from multiple YouTrack issues (batch mode, max 50 issues). Use for: Bulk cleanup of watchlist, Batch removal of unneeded stars, Processing multiple issues at once, Managing starred issues list. Returns: Object with 'successful' array (unstarred issues) and 'failed' array (errors with issue IDs). Note: Operations are processed with concurrency limit (10 concurrent requests) to prevent API overload. Partial success is possible - some issues may succeed while others fail. After completion, fetch the starred list again to verify removals.", {
         issueIds: z
             .array(z.string().min(1))
             .min(1)

package/dist/src/tools/issue-tools.js

@@ -21,7 +21,7 @@ const issueIdsArgs = {
 };
 const issueIdsSchema = z.object(issueIdsArgs);
 const issueCreateArgs = {
-    projectId: z.string().min(1).describe("Project ID (YouTrack internal id)"),
+    projectId: z.string().optional().describe("Project ID (defaults to YOUTRACK_DEFAULT_PROJECT when omitted)"),
     summary: z.string().min(1).describe("Brief issue description"),
     description: z
         .string()
@@ -29,6 +29,22 @@ const issueCreateArgs = {
         .describe("Full description. Supports folded sections: <details> <summary>Title</summary>Content</details>"),
     parentIssueId: z.string().optional().describe("Parent issue ID"),
     assigneeLogin: z.string().optional().describe("Assignee login or me"),
+    stateName: z.string().optional().describe("Initial state name (case-insensitive)"),
+    links: z
+        .array(z.object({
+        linkType: z.string().min(1).describe("Link type name or id (e.g., 'Subtask')"),
+        targetId: z.string().min(1).describe("Target issue code or readable id"),
+        sourceId: z
+            .string()
+            .optional()
+            .describe("Source issue code override (defaults to the new issue)"),
+        direction: z
+            .enum(["inbound", "outbound"])
+            .optional()
+            .describe("Direction relative to the new issue (default: outbound)"),
+    }))
+        .optional()
+        .describe("Optional array of links to create after issue creation"),
     usesMarkdown: z.boolean().optional().describe("Use Markdown formatting"),
 };
 const issueCreateSchema = z.object(issueCreateArgs);
@@ -114,15 +130,17 @@ export function registerIssueTools(server, client) {
             return errorResponse;
         }
     });
-    server.tool("issue_create", "Create new issue in YouTrack. Supports markdown with folded sections (<details>/<summary>) in description. Note: Response includes standard fields only (id, idReadable, summary, description, wikifiedDescription, usesMarkdown, project, parent, assignee). Custom fields are not included.", issueCreateArgs, async (rawInput) => {
+    server.tool("issue_create", "Create new issue in YouTrack. Supports markdown with folded sections (<details>/<summary>) in description. Note: Response includes standard fields only (id, idReadable, summary, description, wikifiedDescription, usesMarkdown, project, parent, assignee). Custom fields are not included. After the call, fetch the created issue again to confirm that every requested property (assignee, state, links, etc.) was applied by YouTrack.", issueCreateArgs, async (rawInput) => {
         try {
             const payload = issueCreateSchema.parse(rawInput);
             const issue = await client.createIssue({
-                project: payload.projectId,
+                projectId: payload.projectId,
                 summary: payload.summary,
                 description: payload.description,
                 parentIssueId: payload.parentIssueId,
                 assigneeLogin: payload.assigneeLogin,
+                stateName: payload.stateName,
+                links: payload.links,
                 usesMarkdown: payload.usesMarkdown,
             });
             const response = toolSuccess(issue);
@@ -133,7 +151,7 @@ export function registerIssueTools(server, client) {
             return errorResponse;
         }
     });
-    server.tool("issue_update", "Update existing issue. Supports markdown with folded sections (<details>/<summary>) in description. Note: Response includes standard fields only (id, idReadable, summary, description, wikifiedDescription, usesMarkdown, project, parent, assignee). Custom fields are not included.", issueUpdateArgs, async (rawInput) => {
+    server.tool("issue_update", "Update existing issue. Supports markdown with folded sections (<details>/<summary>) in description. Note: Response includes standard fields only (id, idReadable, summary, description, wikifiedDescription, usesMarkdown, project, parent, assignee). Custom fields are not included. Always re-fetch the issue after the update to verify that each requested change was applied.", issueUpdateArgs, async (rawInput) => {
         try {
             const payload = issueUpdateSchema.parse(rawInput);
             if (payload.summary === undefined &&
@@ -156,7 +174,7 @@ export function registerIssueTools(server, client) {
             return errorResponse;
         }
     });
-    server.tool("issue_assign", "Assign assignee to issue. Note: Response includes standard fields only (id, idReadable, summary, description, wikifiedDescription, usesMarkdown, project, parent, assignee). Custom fields are not included.", issueAssignArgs, async (rawInput) => {
+    server.tool("issue_assign", "Assign assignee to issue. Note: Response includes standard fields only (id, idReadable, summary, description, wikifiedDescription, usesMarkdown, project, parent, assignee). Custom fields are not included. After assignment, fetch the issue again to ensure the new assignee is set.", issueAssignArgs, async (rawInput) => {
         try {
             const payload = issueAssignSchema.parse(rawInput);
             const issue = await client.assignIssue({
@@ -171,7 +189,7 @@ export function registerIssueTools(server, client) {
             return errorResponse;
         }
     });
-    server.tool("issue_comment_create", "Add comment to issue. Supports markdown with folded sections (<details>/<summary>) for hiding logs, code examples, etc. Note: Response includes comment fields - id, text, textPreview, usesMarkdown, author (id, login, name), created, updated, commentUrl (direct link to comment).", issueCommentCreateArgs, async (rawInput) => {
+    server.tool("issue_comment_create", "Add comment to issue. Supports markdown with folded sections (<details>/<summary>) for hiding logs, code examples, etc. Note: Response includes comment fields - id, text, textPreview, usesMarkdown, author (id, login, name), created, updated, commentUrl (direct link to comment). Reload the comments list if you need to confirm formatting or visibility.", issueCommentCreateArgs, async (rawInput) => {
         try {
             const payload = issueCommentCreateSchema.parse(rawInput);
             const comment = await client.createIssueComment({
@@ -187,7 +205,7 @@ export function registerIssueTools(server, client) {
             return errorResponse;
         }
     });
-    server.tool("issue_comment_update", "Update existing issue comment. Supports markdown with folded sections (<details>/<summary>). Note: Response includes comment fields - id, text, textPreview, usesMarkdown, author (id, login, name), created, updated, commentUrl (direct link to comment). Use for: Editing comment text, changing formatting mode, correcting typos in comments.", issueCommentUpdateArgs, async (rawInput) => {
+    server.tool("issue_comment_update", "Update existing issue comment. Supports markdown with folded sections (<details>/<summary>). Note: Response includes comment fields - id, text, textPreview, usesMarkdown, author (id, login, name), created, updated, commentUrl (direct link to comment). Use for: Editing comment text, changing formatting mode, correcting typos in comments. After updating, fetch the comment again if you need to confirm rendered content.", issueCommentUpdateArgs, async (rawInput) => {
         try {
             const payload = issueCommentUpdateSchema.parse(rawInput);
             if (payload.text === undefined && payload.usesMarkdown === undefined) {
@@ -245,7 +263,7 @@ export function registerIssueTools(server, client) {
             return errorResponse;
         }
     });
-    server.tool("issue_change_state", "Change issue state/status using state machine transitions. Use for: Moving issues through workflow states (e.g., from 'Open' to 'In Progress'), updating issue status, triggering state transitions. Note: Only valid transitions are allowed based on current state and workflow rules. The tool automatically discovers available transitions and validates the requested state change. Returns information about the previous state, new state, and the transition used.", issueChangeStateArgs, async (rawInput) => {
+    server.tool("issue_change_state", "Change issue state/status using state machine transitions. Use for: Moving issues through workflow states (e.g., from 'Open' to 'In Progress'), updating issue status, triggering state transitions. Note: Only valid transitions are allowed based on current state and workflow rules. The tool automatically discovers available transitions and validates the requested state change. Returns information about the previous state, new state, and the transition used. After the transition, fetch issue details again to ensure the state is what you expect.", issueChangeStateArgs, async (rawInput) => {
         try {
             const payload = issueChangeStateSchema.parse(rawInput);
             const result = await client.changeIssueState({

package/dist/src/tools/workitem-tools.js

@@ -132,7 +132,7 @@ export function registerWorkitemTools(server, client) {
             return errorResponse;
         }
     });
-    server.tool("workitem_create", "Create work item record. Supports markdown with folded sections (<details>/<summary>) in description. Note: Response includes predefined fields only - id, date, duration (minutes, presentation), text, textPreview, usesMarkdown, description, issue (id, idReadable), author (id, login, name, email).", workItemCreateArgs, async (rawInput) => {
+    server.tool("workitem_create", "Create work item record. Supports markdown with folded sections (<details>/<summary>) in description. Note: Response includes predefined fields only - id, date, duration (minutes, presentation), text, textPreview, usesMarkdown, description, issue (id, idReadable), author (id, login, name, email). After the call, re-fetch work items to confirm the new record appears with expected duration and description.", workItemCreateArgs, async (rawInput) => {
         try {
             const payload = workItemCreateSchema.parse(rawInput);
             const item = await client.createWorkItemMapped({
@@ -151,7 +151,7 @@ export function registerWorkitemTools(server, client) {
             return errorResponse;
         }
     });
-    server.tool("workitem_create_idempotent", "Create work item record if similar one does not exist. Supports markdown with folded sections (<details>/<summary>) in description. Note: Response includes predefined fields only - id, date, duration (minutes, presentation), text, textPreview, usesMarkdown, description, issue (id, idReadable), author (id, login, name, email).", workItemIdempotentArgs, async (rawInput) => {
+    server.tool("workitem_create_idempotent", "Create work item record if similar one does not exist. Supports markdown with folded sections (<details>/<summary>) in description. Note: Response includes predefined fields only - id, date, duration (minutes, presentation), text, textPreview, usesMarkdown, description, issue (id, idReadable), author (id, login, name, email). After creation, reload work items to verify whether the entry was newly added or an existing one was reused.", workItemIdempotentArgs, async (rawInput) => {
         try {
             const payload = workItemIdempotentSchema.parse(rawInput);
             const item = await client.createWorkItemIdempotent({
@@ -169,7 +169,7 @@ export function registerWorkitemTools(server, client) {
             return errorResponse;
         }
     });
-    server.tool("workitem_update", "Update work item record. Supports markdown with folded sections (<details>/<summary>) in description. Note: Response includes predefined fields only - id, date, duration (minutes, presentation), text, textPreview, usesMarkdown, description, issue (id, idReadable), author (id, login, name, email).", workItemUpdateArgs, async (rawInput) => {
+    server.tool("workitem_update", "Update work item record. Supports markdown with folded sections (<details>/<summary>) in description. Note: Response includes predefined fields only - id, date, duration (minutes, presentation), text, textPreview, usesMarkdown, description, issue (id, idReadable), author (id, login, name, email). After updating, fetch the work item again to confirm the new values were applied.", workItemUpdateArgs, async (rawInput) => {
         try {
             const payload = workItemUpdateSchema.parse(rawInput);
             if (payload.date === undefined &&
@@ -195,7 +195,7 @@ export function registerWorkitemTools(server, client) {
             return errorResponse;
         }
     });
-    server.tool("workitem_delete", "Delete work item record", workItemDeleteArgs, async (rawInput) => {
+    server.tool("workitem_delete", "Delete work item record. After deletion, list work items again to ensure the record was removed.", workItemDeleteArgs, async (rawInput) => {
         try {
             const payload = workItemDeleteSchema.parse(rawInput);
             const result = await client.deleteWorkItem(payload.issueId, payload.workItemId);
@@ -207,7 +207,7 @@ export function registerWorkitemTools(server, client) {
             return errorResponse;
         }
     });
-    server.tool("workitems_create_period", "Create work items for period. Supports markdown with folded sections (<details>/<summary>) in description. Note: Created work items include predefined fields only - id, date, duration (minutes, presentation), text, textPreview, usesMarkdown, description, issue (id, idReadable), author (id, login, name, email).", workItemsPeriodArgs, async (rawInput) => {
+    server.tool("workitems_create_period", "Create work items for period. Supports markdown with folded sections (<details>/<summary>) in description. Note: Created work items include predefined fields only - id, date, duration (minutes, presentation), text, textPreview, usesMarkdown, description, issue (id, idReadable), author (id, login, name, email). After bulk creation, reload work items to validate that each day received the expected entry.", workItemsPeriodArgs, async (rawInput) => {
         try {
             const payload = workItemsPeriodSchema.parse(rawInput);
             const result = await client.createWorkItemsForPeriod({