paperclip-mcp
Related Servers
Alternatives to paperclip-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for inter-agent communication. Gives multiple Claude Code sessions a shared message board, agent registry, and orchestration layer — backed by a cloud relay so agents can coordinate across machines, repos, and teams.845 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server that enables Claude Code to communicate with other Claude Code agents over HTTP, allowing users to ask questions about remote codebases or delegate coding tasks.MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for integrating Linear with Claude Code and other MCP clients. Enables issue management, project planning, and status tracking through a set of tools.-
- AlicenseAqualityDmaintenanceMCP server that spawns autonomous Claude Code agents in GitHub repos, enabling task delegation with persistent state, multi-step workflows, and job monitoring.4779 npm2Apache 2.0
- AlicenseAqualityAmaintenanceMCP server for Claude Code agents to manage persistent shared task boards with dependency graphs, atomic claims, and git-bound tasks.11MIT
- FlicenseNot gradedqualityDmaintenanceMCP server and automation watcher for Plane project management, enabling Claude to interact with Plane via 40+ tools and auto-trigger on labeled issues.-
TDQS
Scored across 104 tools
Most tools target a distinct resource and action, and descriptions do a good job of cross-referencing siblings. However, there are several genuinely confusable pairs — invoke_heartbeat vs wakeup_agent, create_agent vs create_agent_hire vs create_approval, and update_agent vs set_agent_instructions_path — that an agent would need to study closely to disambiguate. At 104 tools, the cumulative surface creates real selection risk.
The paperclip_ prefix plus snake_case verb_noun naming is used consistently across nearly all tools, making the overall pattern highly predictable. Minor deviations exist, such as bare verbs like approve and reject (rather than approve_approval/reject_approval) and the semantically overlapping invoke_heartbeat vs wakeup_agent pair, but these are exceptions rather than the rule.
With 104 tools, this server far exceeds even a generous MCP surface and lands in the extreme-count category. While the domain is broad, agents would be overwhelmed by hundreds of choices, and many tools could be consolidated or split into separate domain-specific MCP servers.
The surface is remarkably broad, covering agents, companies, goals, projects, issues, approvals, routines, plugins, secrets, costs, feedback traces, and import/export flows. However, there are notable dead ends: paperclip_delete_routine and the plugin uninstall flow are referenced in descriptions but no such tools exist in the set, and several resources (labels, secrets, goals, projects) lack delete operations.