notra
OfficialRelated Servers
Alternatives to notra
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables LLM clients to interact with Substack's API for automations like creating posts and managing drafts.27832 npm76MIT
- FlicenseAqualityBmaintenanceEnables an LLM to read and write NetBox data through its REST API, supporting listing endpoints, inspecting schemas, and creating, updating, or deleting objects.7-

@vertracloud/mcpofficial
AlicenseBqualityAmaintenanceEnables AI assistants to operate Vertra Cloud resources through the public API: deploy and manage applications, view logs and metrics, create and restore snapshots, and administer databases and environment variables.991MIT- FlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with Novu's notification infrastructure, supporting event triggering, subscriber management, topic operations, and notification retrieval.-
- AlicenseAqualityCmaintenanceEnables AI coding tools to manage Neural Draft's CMS, blog, social, booking, and commerce features through natural language, bridging AI-generated frontends with backend business logic.3828 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables LLMs to manage Clerk applications, domains, application transfers, instance users, JWT templates, and instance configuration via the Clerk Platform API.-
TDQS
Scored across 30 tools
Each tool targets a distinct resource or action. Post, brand identity, integration, schedule, chat, skill, and feedback tools are clearly separated. Async generation and status polling are paired cleanly, avoiding ambiguity.
Most tools follow a verb_noun pattern (e.g., delete_post, create_skill). Minor inconsistencies: 'create_github_integration' is more specific than 'delete_integration', and 'submit_feedback' deviates from the create/update/delete pattern.
30 tools cover multiple subdomains (posts, brand, integrations, schedules, chats, skills, feedback). While slightly high, each tool serves a clear purpose and most CRUD operations are present, making the count reasonable.
Core CRUD operations are present for posts, brand identities, skills, schedules, and chats. Async generation with polling is implemented. Missing update/delete for integrations and feedback lifecycle (no list/update/delete for feedback) are minor gaps.