@promptjang/mcp-server
OfficialRelated Servers
Alternatives to @promptjang/mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables storage, versioning, and retrieval of prompts with rich metadata via MCP tools, supporting stdio and SSE transports.37 npm3ISC
- AlicenseAqualityBmaintenanceEnables an AI agent to run local tools on the user's own machine via stdio, including command execution, workspace file read/write, and system status checks.52MIT
- AlicenseAqualityCmaintenanceEnables LLM agents to send, receive, and discover contacts on the agentic message bus via native tools.5MIT

PoYo MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceLocal stdio bridge to the hosted PoYo MCP server, enabling discovery and execution of AI models via chat, generation tasks, and agent skills.1MIT- AlicenseAqualityDmaintenanceStart, observe, and interact with Claude Managed Agents from any MCP client — launch an agent, watch its events, reply, approve the tools it wants to run, and stop it. Runs over stdio, HTTP, or AWS Lambda with pluggable auth.171MIT
- FlicenseNot gradedqualityCmaintenanceAn MCP host that integrates a CLI agent with local todo servers over stdio and authenticated Streamable HTTP, supporting progressive skill loading for task management and daily planning workflows.-
TDQS
Scored across 10 tools
Each tool targets a distinct resource or action, and the descriptions make the boundaries clear. The only mild overlap is between list_targets and list_mailboxes, since mailbox targets and durable mailboxes are related, but the descriptions differentiate them well.
Tool names consistently follow a verb_noun snake_case pattern: list_*, get_*, claim_*, ack_*, send_*, replay_*. This makes the set highly predictable and easy to navigate.
Ten tools is well-scoped for an event, mailbox, and usage monitoring server. Each tool serves a clear purpose without redundancy or bloat.
The core lifecycle is covered: send events, inspect delivery, replay failed events, list/read/claim/acknowledge mailbox messages, and check usage. A minorgap is the lack of a list-events endpoint to browse past events without knowing their IDs, but agents can work around this.