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

PipesHub MCP Serverofficial
AlicenseAqualityAmaintenanceEnables clients to interact with PipesHub data and functionality through MCP, including chat, search, record retrieval, directory browsing, sources, and agents.72,265 npm7Apache 2.0- AlicenseNot gradedqualityDmaintenanceExposes WebVoice REST API tools to MCP clients for voice, chat, translation, and image generation via natural language.22 PyPIMIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to place, monitor, and hang up phone calls through authenticated tools, retrieve transcripts, and exchange correlated task results with a waiting host. It supports simulated or live calling with persisted call lifecycle records, duration limits, and idempotent requests.MIT
- AlicenseBqualityBmaintenanceEnables MCP clients to manage AI voice assistants, place calls, run campaigns, handle contacts and knowledge bases, and read call transcripts. It also provides account, phone number, dialer, and analytics tools through a hosted or local MCP connection.25MIT
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.