Zelinqa MCP
OfficialRelated Servers
Alternatives to Zelinqa MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP clients to submit completed speech or typed text to a self-hosted decision engine and receive judgments such as ordinary speech, command, retained thought, uncertainty, or no action, along with session and decision inspection.3MIT
- AlicenseNot gradedqualityDmaintenanceEnables to run structured QuReDec decision briefs from inside MCP-compatible clients, submitting questions and receiving evidence-backed recommendations with citations.19 PyPIMIT
- AlicenseNot gradedqualityAmaintenancePublic MCP server for agent-created, human-friendly, short-lived surveys. Enables agents to ask structured questions and retrieve answers.2MIT
- FlicenseBqualityCmaintenanceEnables MCP clients to manage conversations, handoffs, context packets, audits, and publishing through the LNKZ REST relay, while exposing resources and prompts for context-aware workflows.24-
- AlicenseNot gradedqualityCmaintenanceEnables AI-driven customer support operations including conversation management, knowledge base, contacts, metrics, and settings via MCP.MIT
- AlicenseNot gradedqualityCmaintenanceEnables authorized clients to invoke tenant-aware conversational assistant tools and resources over MCP, including durable conversations, agent configuration, connector policies, and PostgreSQL-backed data.Apache 2.0
TDQS
Scored across 7 tools
Most tools have clear distinct roles (start, status, feedback, forget, next_question), but adjust, add_context and next_question all send information 'without consuming a turn', creating subtle boundaries an agent could misselect between. The detailed descriptions largely resolve this.
All names share a consistent zelinqa_ prefix and are readable, though there is minor mixing of verb forms (adjust, start, forget) with noun forms (status, feedback, next_question). The pattern is predictable enough.
Seven tools is well within the ideal range and each maps to a distinct step in the conversation lifecycle. Nothing feels padded or missing at the count level.
The set covers the full guided-conversation lifecycle: start/recover, advance (next_question), inspect (status), enrich (adjust, add_context), report outcome (feedback), and release (forget). Minor gaps like an explicit conversation-list or end tool are workable around.