# MCP: support

Source: <https://telegafirst.com/docs/mcp-support>
Locale: ru
releaseGitSha: 0bb11ef116e17ec64c802d5476eaff442e53d252
sourceContentDigest: 9e13d5333da4405cd77acd5b08da8a22d5dd7d12f6b4682b3ab556e4ec3f5966
Version: 9

# MCP: support

Определения инструментов. Обновляйте tools/list после изменения прав. required\_scopes: ALL.

## support\_ticket\_create

Escalate to the TelegaFirst team when you could NOT solve the problem yourself: \`kind:"bug\_report"\` (requires title, description, ai\_diagnosis, ai\_evidence and priority — diagnose FIRST, and ask the person for anything you are missing rather than filing a blank) or \`kind:"suggestion"\` (title, description, ai\_diagnosis only; it takes no evidence and no priority). Duplicates are handled INSIDE this tool: identical reports collapse onto the existing ticket. ALWAYS relay the result — \`outcome:"created"\` means a new #ticket\_number, \`outcome:"attached"\` means your report joined an existing one and the answer will reach you there. Filing does NOT close anything: only a human resolves a ticket, and the resolution comes back to the account owner in Telegram.

Scopes (ALL): \["support:write"]. Risk: "write".

[Вход, результат и права](https://telegafirst.com/docs/mcp-tool-support-ticket-create)

## support\_ticket\_list

List THIS account's support tickets with the TelegaFirst platform — what was reported, its priority and lifecycle state (OPEN / IN\_PROGRESS / RESOLVED / CLOSED / WONT\_FIX), how it was resolved, and how many separate contacts were glued into it. Pass \`status\` to narrow, \`limit\` to page. Use it before filing anything: an OPEN ticket about the same breakage means the answer is already on its way. Returns only this account's tickets. 0-cost read.

Scopes (ALL): \["support:read"]. Risk: "read".

[Вход, результат и права](https://telegafirst.com/docs/mcp-tool-support-ticket-list)