lnkz-mcp
Related Servers
Alternatives to lnkz-mcp
No user-submitted related servers found.
Related Servers
- 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
- AlicenseNot gradedqualityCmaintenanceEnables agents to discover rooms, read conversations, register, create rooms, post messages, and reply through MCP or HTTP with bearer-token authentication.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to place and manage outbound phone calls, handle inbound calls with a realtime voice agent, add live context, send DTMF digits, and retrieve structured call outcomes and transcripts.MIT
- AlicenseNot gradedqualityCmaintenanceEnables independently operated AI clients to exchange private 1:1 messages and files using authenticated participant identities, with retry deduplication, status tracking, notifications, and owner conversation inspection. Provides REST and MCP tools for messaging, attachments, subscriptions, and replay.MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to discover and connect over MQTT, list and invoke tools, and read resources in browser and Node.js environments.4 npmMIT

PipesHub MCP Serverofficial
AlicenseAqualityBmaintenanceEnables clients to interact with PipesHub data and functionality through MCP, including chat, search, record retrieval, directory browsing, sources, and agents.74,436 npm17Apache 2.0
TDQS
Scored across 24 tools
Most tools have clearly distinct purposes, but some close pairs exist such as save_conversation vs. import_conversation vs. append_messages, and search_conversations vs. search_context. Descriptions are detailed enough to disambiguate, though a couple of analytic/export tools could be confused at a glance.
The naming is predominantly consistent snake_case verb_noun (save_conversation, list_handoffs, build_context_graph). A few outliers like workspace_stats and audit_log are noun-first rather than verb-first, but the pattern is otherwise uniform and readable.
At 24 tools, the surface is on the heavy side and exceeds the typical 3-15 well-scoped range. Each tool appears to have a reason to exist, but the count feels more like a full platform API than a focused MCP server, making it borderline.
The tool set covers the full conversation lifecycle: save/import/get/list/delete/append/export, handoff creation/redemption/continuation/revocation, analytics, search across connectors, and audit logging. No major gaps are apparent for the stated purpose of managing portable conversations and handoffs.