alfred-voc-analysis-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@alfred-voc-analysis-mcp analyze recent VoC trends and emerging signals"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Alfred VoC Analysis MCP v0.1
An MCP server that transforms Heum Alfred/DESK VoC facts into CX intelligence. The structure is explicitly separated into Fact → Analysis → Synthesis.
Architecture
fact.py:FactRepositoryto be implemented by DB/API adapters; Facts do not store AI interpretation.analysis.py: computes overview, issue intelligence, CX concern, emerging signal, trend driver, and resolution effect in deterministic Python.synthesis.py: assembles the detailed Report, Executive Brief, and improvement Planning Signal DTO.server.py: FastMCP tool adapter. The analysis core does not depend on MCP or an external LLM.
The input schema preserves source extension fields with FactRecord(extra="allow"). It does not change the actual DB schema; production DB/API connections are added via the FactRepository adapter.
Related MCP server: NPS Chatbot MCP Server
MCP tools
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
Issue tools intentionally share one portfolio assessment so Frequency alone cannot contradict Priority Movement. Each issue result returns evidence, reason and confidence.
Run
python -m venv .venv
pip install -e ".[dev]"
pytest
alfred-voc-analysis-mcpv0.1 ships an in-memory reference adapter. Embed the service and call configure_records, or implement FactRepository for voc-management DB/API.
Calibration
AnalysisConfig contains data-sufficiency and observation-window settings. Defaults are conservative technical defaults, not Heum policy. No opaque weighted score or fixed “N건=High” business rule is used.
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.4MIT
- 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.-