@perssua/mcp
OfficialRelated Servers
Alternatives to @perssua/mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceConnects your personal Althea AI assistant to MCP-compatible tools like Codex and Claude, allowing you to send messages and retrieve conversation history.21 PyPIMIT
- AlicenseNot gradedqualityCmaintenanceEnables authorized clients to invoke tenant-aware conversational assistant tools and resources over MCP, including durable conversations, agent configuration, connector policies, and PostgreSQL-backed data.Apache 2.0
- FlicenseNot gradedqualityCmaintenanceLets AI assistants manage subscribers, trigger workflows, inspect notification events, and tune preferences across any MCP-compatible client.-
- AlicenseAqualityNot gradedmaintenanceEnables AI assistants to discover, retrieve details about, and manage MCP (Model Context Protocol) servers that provide additional tools and capabilities on demand.563 npm10-
- FlicenseBqualityDmaintenanceProvides a standardized way to integrate Perplexity AI's features like chat, search, and documentation access into MCP-based systems.51-

Anam MCP Serverofficial
AlicenseBqualityCmaintenanceEnables managing AI personas, avatars, voices, and sessions from any MCP client, for integration with Anam AI.5430MIT
TDQS
Scored across 5 tools
Each tool maps to a distinct action: environment status, assistant listing, remote link creation, local session launch, and assistant creation. The two session-starting tools are clearly separated by local vs remote context and explicitly reference each other, reducing ambiguity.
Most tool names follow a clear verb_noun snake_case pattern: list_assistants, create_session_link, start_session, create_assistant. app_status is the only noun-phrase name without an action verb, a minor deviation from the otherwise consistent convention.
Five tools is well-scoped for a desktop-app integration bridge. Each tool covers a distinct step in the assistant/session workflow without unnecessary overlap or bloat.
The set covers the core workflow: checking app availability, listing assistants, starting sessions locally or via links, and creating new assistants. It lacks update/delete or session-management operations, but those may realistically live in the desktop app itself.