cloneai-agent-hub
Related Servers
Alternatives to cloneai-agent-hub
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables agents to inspect machine status and sensor anomalies, search maintenance guidance, and create maintenance tickets through controlled MCP tools.-
- FlicenseCqualityDmaintenanceEnables semantic search over knowledge-base articles and listing of sample support tickets using MCP tools.4-
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to search Japanese landing-page design systems and pattern packs, inspect their DESIGN.md files, and retrieve them for use in projects through MCP tools without writing files itself.66 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables users to search jobs, retrieve job details, and view or update their LAPRAS career profile, including work experiences, job summaries, career aspirations, and technical skills through MCP tools.-

Teletype MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI assistants to find and read customer conversations, look up profiles, send replies, manage workspace metadata, and handle daily support workflows. It also supports triage, drafting, escalation, and handover tasks through MCP tools, prompts, and resources.45 npm1MIT- AlicenseNot gradedqualityBmaintenanceEnables agents to list brands, compose prompts, generate or draw assets, check compliance, and manage review workflows through MCP tools.Apache 2.0
TDQS
Scored across 6 tools
The two prefixes cleanly separate the CloneAI survey tools from the Agent Hub knowledge tools, and the survey-vs-poll pair (synthetic_persona_survey returns 'running' with next_tool = get_survey_result) is explicitly linked in the descriptions. The main soft spot is agent_hub_status, which bundles templates and pointers for searching, reading, preparing contributions, and running surveys, so an agent could pick it instead of the dedicated query/read/prepare tools.
All names are snake_case with predictable service prefixes (cloneai_*, agent_hub_*) and verb/object phrasing (query_memory, read_entry, prepare_contribution, get_survey_result). Minor inconsistency: the survey tool is noun-phrased (synthetic_persona_survey) rather than verbed, and an undocumented alias 'hub_status' exists for agent_hub_status.
Six tools is tight and purpose-driven: two for running/fetching surveys, three for Hub search/read/prepare, one for discovery/status. Nothing looks redundant enough to cut, and there's no bloat.
The surface covers the full survey lifecycle (start, wait/poll, fetch latest 3h demo) plus Hub search, read with replies, and contribution preparation. Posting itself is deliberately delegated to the client's own HTTP call and no tool lists or cancels survey jobs, but these are intentional or workable gaps rather than dead ends.