MCP Server for TehProf Support — AI-powered helpdesk management. Streamable HTTP transport for remote AI clients with tier-gated tool access.
Server has 31 well-named tools with consistent verb_noun patterns (knowledge_search, demo_create_ticket, channels_configure). All tools have descriptions (avg ~120 chars, within baseline 34-392 range). Input schemas present for all tools with proper JSON Schema structure. However, several critical gaps: (1) output schemas are NOT documented, LLMs cannot predict response structure for chaining; (2) many parameter descriptions lack format/constraint details (e.g., 'slug' in knowledge_read has no example format); (3) no error handling guidance in descriptions; (4) some parameters missing descriptions entirely (e.g., 'conditions' and 'actions' in automation_rules_create are described as 'object' with only examples, no type details); (5) no pagination guidance despite tools returning lists (knowledge_list, analytics_operators, bitrix_contacts). Tier-gating system is well-designed but not reflected in tool descriptions for clarity.
Get support dashboard overview: open tickets, SLA compliance, average response time, ticket volume trends.
Get operator performance report: tickets handled, avg response time, resolution rate, customer satisfaction per operator.
Get SLA compliance report: response time metrics, breach count, compliance percentage by priority.
Create a new automation rule. Define trigger event, conditions, and actions.
List automation rules: auto-assignment, auto-reply, escalation, notification triggers.
Enable or disable an automation rule.
Output schemas not documented. LLMs cannot predict response structure, breaking tool chaining and forcing exploratory calls. Every tool should document what fields it returns.
Complex object parameters (conditions, actions, config) lack type details. automation_rules_create 'conditions' and 'actions' described only as 'object' with examples, no schema for nested fields. LLMs cannot construct valid payloads.
No pagination guidance for list tools. knowledge_list, analytics_operators, bitrix_contacts return unbounded results. Should document limit defaults, max values, and cursor/offset support.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | B | 70 | <=2025-11-25 | v2 |
Search and list CRM contacts from Bitrix24. Uses your tenant's Bitrix24 integration.
List CRM deals from Bitrix24. Filter by stage, responsible person, or search.
Create a task in Bitrix24 linked to a support ticket. Syncs status updates between systems.
List tasks from Bitrix24. Can filter by status and responsible user.
List Bitrix24 portal users (employees). Useful for finding who to assign tasks to.
Configure a messaging channel. Set up webhook URLs, API keys, and channel-specific settings.
List all configured messaging channels (WhatsApp, Telegram, Email, MAX) with their connection status.
Check connection status of a specific channel. Useful for diagnosing delivery issues.
Create a demo ticket in sandbox mode to try out the support system. Demo tickets are auto-deleted after 24 hours. Great for testing workflows.
View a demo ticket to see how ticket details look. Shows status, priority, messages, and available actions.
Show a complete ticket lifecycle demo: creation → assignment → response → resolution. Explains how the support workflow works step by step.
List all available knowledge base articles grouped by category. Use this to explore what documentation is available.
Read a specific knowledge base article by slug. Returns full markdown content of the article.
Search the Support knowledge base for articles about features, setup guides, API integration, and troubleshooting. Matches article title, slug, category and full content. Returns ranked matches with title and snippet.
List all features available on your current plan and what you get by upgrading. Great for understanding the full potential of TehProf Support.
Get step-by-step setup guide for TehProf Support. Shows what to configure based on your current plan, with tips on what to set up first.
Calculate which plan is best based on your team size and needs. Provides a personalized recommendation.
Show all available pricing plans with features, limits, and prices. Helps users choose the right plan for their needs.
Get current tenant settings: company info, business hours, SLA rules, channels, widget config, bot settings. Shows which settings are available on your plan.
List operators in your team with their roles and status. On free plan: shows your single operator. Higher plans: full team management.
Update tenant settings. Only settings available on your current plan can be modified. AI will suggest upgrades for locked settings.
Check TehProf Support platform health and uptime status.
Get information about TehProf Support platform: what it is, who it is for, key capabilities, supported languages and integrations.
Get information about your tenant (company) — current plan, usage, limits, and configured features. Requires authentication.
List configured outgoing webhooks with their event subscriptions and delivery stats.
No error recovery guidance in descriptions. Tools lack actionable error messages (e.g., 'If slug not found, call knowledge_list to discover available articles'). Agents cannot self-correct on failures.
Parameter format constraints missing. 'slug' in knowledge_read, 'deadline' in bitrix_task_create, and 'query' in knowledge_search lack format examples or constraints. LLMs may pass invalid formats.