alfred-voc-analysis-mcp
Alfred VoC Analysis MCP v0.1
Это MCP-сервер, который преобразует факты Heum Alfred/DESK VoC в CX-аналитику. Структура явно разделена на Fact → Analysis → Synthesis.
Архитектура
fact.py:FactRepository, который реализуют адаптеры БД/API; в Fact не сохраняется AI-интерпретация.analysis.py: вычисляет обзор, аналитику проблем, CX-риски, зарождающиеся сигналы, драйверы трендов и эффект от устранения проблем с помощью детерминированного Python.synthesis.py: собирает подробный отчёт, Executive Brief и DTO сигналов для улучшений.server.py: адаптер инструментов FastMCP. Ядро анализа не зависит от MCP или внешних LLM.
Входная схема — FactRecord(extra="allow"), что сохраняет расширенные поля источника. Фактическая схема БД не изменяется; подключение к production БД/API добавляется через адаптер FactRepository.
Related MCP server: NPS Chatbot MCP Server
Инструменты MCP
get_voc_overviewanalyze_issue_frequency,analyze_issue_severity,analyze_issue_persistenceanalyze_unresolved_issues,rerank_issue_priorities,compare_issue_portfolioanalyze_customer_experiencedetect_emerging_signalsanalyze_voc_trendsanalyze_resolution_effectbuild_report_dataset,build_executive_brief,build_improvement_signals
Инструменты для проблем намеренно используют единую оценку портфеля, чтобы частота сама по себе не могла противоречить движению приоритетов. Каждый результат по проблеме возвращает evidence, reason и confidence.
Запуск
python -m venv .venv
pip install -e ".[dev]"
pytest
alfred-voc-analysis-mcpВ v0.1 поставляется эталонный адаптер в памяти. Встройте сервис и вызовите configure_records или реализуйте FactRepository для БД/API управления VoC.
Калибровка
AnalysisConfig содержит настройки достаточности данных и окна наблюдения. Значения по умолчанию — консервативные технические значения по умолчанию, а не политика Heum. Не используется непрозрачный взвешенный балл или фиксированное бизнес-правило вида «N건 = High».
Available Tools
14 toolsanalyze_customer_experienceD
Inputs: end_date (required), start_date (required). Returns: result
analyze_issue_frequencyD
Inputs: end_date (required), start_date (required). Returns: result
analyze_issue_persistenceD
Inputs: end_date (required), start_date (required). Returns: result
analyze_issue_severityD
Inputs: end_date (required), start_date (required). Returns: result
analyze_resolution_effectD
Inputs: end_date (required), start_date (required). Returns: result
analyze_unresolved_issuesD
Inputs: end_date (required), start_date (required). Returns: result
analyze_voc_trendsD
Inputs: end_date (required), start_date (required). Returns: object
build_executive_briefD
Inputs: end_date (required), start_date (required). Returns: object
build_improvement_signalsD
Inputs: end_date (required), start_date (required). Returns: object
build_report_datasetD
Inputs: end_date (required), start_date (required). Returns: object
compare_issue_portfolioD
Inputs: end_date (required), start_date (required). Returns: result
detect_emerging_signalsD
Inputs: end_date (required), start_date (required). Returns: result
get_voc_overviewD
Inputs: end_date (required), start_date (required), domain, channel, +3 more. Returns: object
rerank_issue_prioritiesD
Inputs: end_date (required), start_date (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 14 tools
Most tools are clearly separated by specific modifiers (frequency, severity, persistence, resolution effect), but a few pairs could be confused, such as analyze_unresolved_issues vs analyze_issue_persistence and detect_emerging_signals vs analyze_voc_trends.
All tool names follow a consistent snake_case verb_noun pattern using predictable verbs like get, analyze, rerank, compare, detect, and build. The repeated analyze_ prefix is systematic and applied to distinct analytical dimensions.
14 tools is well within the ideal 3-15 range for a specialized VOC analysis server. The set balances analytical tools, prioritization, comparison, and reporting outputs without unnecessary fragmentation.
The tool surface covers the full analytical workflow: overview, issue metrics, priorities, portfolio comparison, trends, emerging signals, resolution effectiveness, and report generation. There are no obvious gaps that would leave an agent unable to complete a VOC analysis task.
Related MCP Connectors
Marketing intelligence MCP server providing campaign performance data and analytics tools.
Hybrid human + AI expertise for faster, trusted answers and decisions via MCP Server.
MCP server for VC pitch-deck scoring, thesis-fit matching, and deal-flow management.
An MCP server that automatically collects feedback on your MCP server.
Related MCP Servers
- AlicenseAqualityDmaintenanceMCP server that synthesizes user feedback from multiple sources into actionable insights. Aggregates reviews, support tickets, and survey responses to identify patterns and priorities.423 PyPIMIT
- FlicenseNot gradedqualityBmaintenanceMCP server enabling NPS chatbot interactions, summaries, topic analysis, and example comments via natural language.-

Augentofficial
AlicenseBqualityDmaintenanceMCP server that turns any audio or video source into structured, searchable intelligence for agents, enabling download, transcription, semantic search, speaker identification, and more.226MIT- FlicenseNot gradedqualityDmaintenanceAn MCP server that orchestrates deterministic analytics, benchmarks, recommendations, and forecasting to provide AI-driven campaign analysis and executive reports.-