IndeCX MCP
Related Servers
Alternatives to IndeCX MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables interaction with LimeSurvey API to create and manage surveys, questions, question groups, activate surveys, and export responses through standardized MCP endpoints.-
- AlicenseAqualityBmaintenanceEnables MCP clients to interact with Exact Synergy Enterprise and Exact Globe+ installations, discovering entities and public actions from the OData metadata and safely performing validated reads (with optional allowlisted mutations).87 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables an MCP client to discover ABS datasets, inspect SDMX dimension order and codelists, and run bounded statistical-data queries against the Australian Bureau of Statistics Data API.MIT
- FlicenseNot gradedqualityCmaintenanceMCP server for Simplesat, enabling search of CSAT/NPS survey answers via the Simplesat V1 API. Provides a single tool to query customer feedback with optional filters like date range and filter criteria.-
- FlicenseAqualityDmaintenanceExposes marketing catalogs (offers, assets, campaigns, and computed metrics) to MCP clients, enabling natural language queries and AI-driven marketing analysis.8-
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to query Abnormal Security for threats, message search, remediation history, ATO cases, vendor/BEC data, and opt-in evidence download and response actions.Apache 2.0
TDQS
Scored across 8 tools
The tools cover distinct resources—surveys, branches, blocklist, answers, invites, non-respondents, and categories—so the overall separation is clear. The main risk is list_actions vs get_action, since both relate to surveys and differ mainly by singular/plural and list/get; get_answers vs get_categories could also be confused but descriptions clarify raw vs categorized responses.
All tools use the indecx_ prefix and a snake_case verb_noun pattern, which is consistent and predictable. The minor inconsistency is that collection retrieval mixes list_* (list_actions, list_branches) with get_* (get_answers, get_invites, get_categories), but this is not seriously misleading.
Eight tools is a well-scoped size for a survey feedback MCP; each tool addresses a distinct data need without redundancy. This is comfortably within the ideal 3-15 tool range and no tool feels like filler.
For a read-only survey analytics server, the surface covers the main entities: surveys/questionnaires, branches, responses, invites, non-response, blocklists, and categories. Minor gaps exist, such as no single-response lookup or branch-filtered answers, but agents can work around these with the provided paginated collections.