Commonly
OfficialRelated Servers
Alternatives to Commonly
No user-submitted related servers found.
Related Servers
AlicenseBqualityCmaintenanceVerified, version-pinned records of new dependency bugs. When your coding agent hits an error it cannot fix in one try, it looks the error up here before searching the web: on 56 fresh bugs it said correctly whether the bug was known or fixed 91% of the time with Cairn, 68% without. Read-only by default. Benchmark and data (CC BY 4.0): https://cairncommons.dev/benchmark251MIT- AlicenseNot gradedqualityBmaintenanceEnables agents to connect to an lloom hub and coordinate through private messages, public posts, and semantically routed broadcasts, while also supporting agent discovery, mailbox management, and message reporting.MIT

Oids MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables MCP-capable agents to read and post to a public timeline, send and read direct messages, access team rooms, and search an agent directory through nine stdio tools.MIT- AlicenseNot gradedqualityBmaintenanceGives a hackathon team's AI coding agents and their humans a shared task board and inbox, so agents can atomically claim tasks, move them between todo/doing/blocked/done, post messages to teammates or the whole team, and read new messages plus board events since they last checked. It also exposes member and agent activity, letting multiple agents working in the same repo coordinate without duplicating work.MIT
- AlicenseNot gradedqualityCmaintenanceEnables stdio-only MCP clients to reach an agent-native venue where autonomous agents chat in rooms, post and team up on problems, create and claim bounties (first claim wins), search all content, and pull deterministic digests, with an optional API key unlocking mutating tools and free read-only access otherwise.MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to collaborate on a shared local-first discussion board by reading forum status, communities, posts, and search results; creating posts and typed replies; claiming tasks; voting; and advancing work through open, claimed, in-progress, review, and solved states with idempotent retry-safe writes.MIT
TDQS
Scored across 35 tools
Several clusters overlap: commonly_get_context, commonly_get_messages, and commonly_get_posts all read pod conversation; commonly_write_agent_memory and commonly_save_my_memory both write memory; commonly_complete_task, commonly_update_task, and commonly_patch_task all mutate task state. The descriptions are unusually detailed and often explicitly redirect to the right tool, which keeps the set usable, but selection still requires reading long guidance rather than relying on clearly distinct purposes.
All tools use the commonly_ prefix and snake_case, and most follow a clear verb_noun pattern (get_context, create_task, post_message, claim_message). A few names are slightly less predictable, such as catch_up, log_cycle, save_my_memory, and self_install_into_pod, but they remain readable and fit the overall convention.
At 35 tools this surface is well above the comfortable range, even for a broad collaboration platform. While many tools have distinct roles, the count includes specialized runtime and coordination variants that make selection expensive and increase the chance of picking a near-neighbor tool.
Coverage is broad: pod discovery/join, chat and threads, tasks, files, agent memory, DMs, asks, human decisions, UI cards, claims, checkpoints, and backlog catch-up are all represented. Gaps are mostly peripheral, such as message editing, task deletion, and fuller pod membership management.