runelay
Related Servers
Alternatives to runelay
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceRuns each MCP server once and lets any number of AI agents connect over HTTP with their own keys, per-tool grants and audit logging, plus a shared task list, shared memory and agent-to-agent requests. Enables agents to work as a coordinated team without duplicating processes, credentials or work.7 npmMIT
- AlicenseNot gradedqualityBmaintenanceA self-hosted MCP gateway that gives every coding agent a single endpoint for connected accounts, reusable skills and shared memory. Enables connecting services like Linear, GitHub and Notion once, so Claude Code, Codex, Cursor and others see the same tools and context, with an API key per agent and full call auditing.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to connect to a single MCP endpoint that aggregates many MCP servers and built-in tools, with multi-user authentication, per-user server configuration, encrypted secrets, and a skills hub.MIT
- AlicenseNot gradedqualityBmaintenanceA self-hosted platform that aggregates upstream MCP servers, OpenAPI imports, and remote device connectors behind a single endpoint per profile, with per-agent scoped authorization, tool/prompt/resource catalogs, and approval-based temporary permissions. It also lets administrators distribute skills and connectors to paired devices and export client configurations.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to connect once and access tools from many registered MCP servers plus built-in modules, with multi-user authentication, per-user server/tool toggles, and a skills hub.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to join one shared room over MCP where they message each other, post live status, read and write shared notes, and use shared connections such as Zapier, all from a single self-hosted process. Supports per-agent tokens, join links, OAuth sign-in, and admin tools for managing seats, roles, and tunnels.1 npmMIT
TDQS
Scored across 9 tools
The tools mostly target distinct areas: tool discovery/execution, connection listing, memory, and skills. call_tool and execute overlap slightly because both can invoke tools, and search_tools with an empty query overlaps with list_connections, but the descriptions make the intended distinctions clear enough.
Almost all tools follow a consistent snake_case verb_noun pattern such as call_tool, list_connections, read_memory, search_tools, and write_memory. execute is the only notable deviation as a bare verb, but the overall convention remains predictable.
Nine tools is well scoped for an agent runtime covering tool discovery, execution, memory, and skills. Each tool has a clear role without excessive surface area.
The set covers core workflows: discovering and calling tools, executing chained calls, managing memories, and reading skills. Minor gaps exist, such as no delete_memory or explicit list_memories/list_skills operations, but agents can mostly work around these with search and read tools.