include_local_fields

MCP tool from Yandex Tracker MCP by aikts

(boolean, optional, default: true): Whether to include queue-specific local fields

How to use it

include_local_fields is exposed by the Yandex Tracker MCP MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), and the include_local_fields tool becomes available to the model automatically. See the full listing for setup details and every tool this server provides.

Install Yandex Tracker MCP

claude mcp add yandex-tracker docker "run --rm -i -e TRACKER_TOKEN=your_tracker_token_here -e TRACKER_CLOUD_ORG_ID=your_cloud_org_id_here -e TRACKER_ORG_ID=your_org_id_here -e TRANSPORT=stdio ghcr.io/

FULL YANDEX TRACKER MCP LISTING

Other tools in Yandex Tracker MCP (39)

assignee

(string or int, optional): Assignee login or UID

comment

(string, optional): Worklog comment

comment_id

(int, required): Comment ID

cursor

(string, optional): The nextcursor value returned by the previous call; pass it to fetch the next page (cursor pagination)

description

(string, optional): Version description

due_date

(date, optional): Version due date in YYYY-MM-DD format

duration

(string, required): ISO-8601 duration (e.g. PT1H30M)

expand

(array of strings, optional): Fields to expand in the response. Available options: all, projects, components, versions, types, team, workflows, fields, issueTypesConfig

field

(string, optional): Filter the changelog by a field key (e.g. status)

fields

(optional): Fields to include in the response (e.g., ["key", "name"]). Helps optimize context window usage by selecting only needed fields. If not specified, returns all available fields.

followers

(array of IssueUpdateFollower, optional): Followers - array of objects with id (string, user ID or login)

include_description

(boolean, optional, default: true): Whether to include issue description in the result. Can be large, so use only when needed.

is_add_to_followers

(boolean, optional, default: true): Add comment author to followers

issue

(string, required): ID or key of the issue to link to (e.g. "TEST-123")

issue_id

(string, format: "QUEUE-123")

link_id

(int, required): Link ID (as returned by issuegetlinks)

maillist_summonees

(array of strings, optional): Mailing lists to summon (emails)

markup_type

(string, optional): Use md for YFM (markdown)

name

(string, required): Version name

page

(optional): Page number to return. If not specified, retrieves all pages automatically.

parent

(IssueUpdateParent, optional): Parent issue reference with id (string) and/or key (string, e.g., 'QUEUE-123')

per_page

(optional): Number of items per page (default: 100)

priority

(string, optional): Priority key (from getpriorities tool)

project

(IssueUpdateProject, optional): Project with primary (int, main project shortId) and optional secondary (array of ints)

queue

(string, required): Queue key where to create the issue (e.g., 'MYQUEUE')

queue_id

(string, required): Queue key like "SOMEPROJECT"

relationship

(string, required): Link type describing how issueid relates to the linked issue. One of: relates, is dependent by, depends on, is subtask for, is parent task for, duplicates, is duplicated by, is epic of, has epic

resolution_id

(string, required): The resolution ID to set when closing (e.g., 'fixed', 'wontFix', 'duplicate')

sprint

(array of IssueUpdateSprint, optional): Sprint assignments - array of objects with id (int) field

start

(datetime, optional): Work start datetime (UTC assumed if timezone is not provided)

start_date

(date, optional): Version start date in YYYY-MM-DD format

summary

(string, required): Issue title/summary

summonees

(array of strings, optional): Users to summon (logins or IDs). This is the API way to mention/call users (notifications are triggered by this field, not by @login in text).