RAPPMCP
Related Servers
Alternatives to RAPPMCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceTurns Claude-style skills (SKILL.md files with resources) into callable MCP tools for any agent. Discovers skills from a directory, exposes their instructions and resources, and can execute bundled helper scripts.118 PyPI410MIT
- AlicenseAqualityCmaintenanceExposes local OpenClaw agents as standard MCP tools so any MCP-compatible client can list agents, dispatch tasks, wait for or cancel runs, read session history, and receive voice-optimized replies.5MIT
- AlicenseNot gradedqualityCmaintenanceEnables discovering locally defined tool packages and exposing them to MCP clients and HTTP callers, with configurable lifecycle modes, isolated per-tool environments, subprocess execution, and optional GPU/VRAM allocation.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceTurns any folder of Markdown agent skills into a local MCP server, exposing them as tools, prompts, and resources for MCP-compatible clients.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents and other MCP clients to register, discover, invoke, and route Python-based tools through a lightweight JSON-RPC gateway, while tracking latency, success rates, and errors.MIT
- AlicenseNot gradedqualityCmaintenanceExposes an agent's skills as MCP tools, allowing any MCP client to route requests and load skills on demand from a single .3md file.20 npm1MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct role: chat sends a message, job_status polls an asynchronous chat job, and capabilities reports server/model/agent information. There is no overlapping purpose, and the descriptions explain exactly when to use each.
Names are all lowercase but follow different conventions: 'chat' is a bare noun, 'job_status' is a snake_case noun phrase, and 'capabilities' is a plural noun. The set is readable, but there is no consistent verb_noun or resource_action pattern.
Three tools are reasonable for a focused AI chat server: send a message, poll long-running work, and inspect capabilities. It is slightly thin but each tool earns its place.
The surface covers the core lifecycle: starting a chat, handling long-running chats asynchronously, polling their status, and discovering capabilities. Minor gaps exist around explicit session management or cancellation, but normal workflows are covered.