No user-submitted related servers found.
Scored across 53 tools
Several tools have overlapping search and memory purposes: mullet_search, trawl_search, trawl_search_pool, trawl_search_multi, trawl_summarize, mullet_remember, and trawl_memory_* all compete for similar retrieval/storage intents. Execution tools also blur together: mullet_run, mullet_opencode, mullet_delegate, mullet_swarm, and trawl_run_agent all perform routed LLM work with subtle boundary distinctions that an agent must parse carefully.
The mullet_ and trawl_ prefixes provide a useful top-level grouping, and all names are snake_case. However, within trawl the convention is mixed: some tools use action_resource order (trawl_search_entities, trawl_get_pool, trawl_load_pool) while others use resource_action order (trawl_agents_list, trawl_pool_delete, trawl_memory_store, trawl_workflow_create).
At 53 tools, the surface is very large and heavy for a single server, spanning orchestration, search, ingestion, graph operations, memory, workflows, agents, prompts, and docs. While these are related platform capabilities, the count far exceeds a well-scoped set and increases selection burden.
The surface covers many lifecycle operations, including memory store/search/list/delete, workflow create/list/status/update, pool management, ingestion, graph build/stats/export, agents, prompts, and docs lookup. But there are notable gaps such as no clear entity or relationship update/delete beyond graph pruning, no task cancellation or explicit active-task listing, and limited update/delete coverage for prompts and agents.