notra
OfficialRelated Servers
Alternatives to notra
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables LLM clients to interact with Substack's API for automations like creating posts and managing drafts.27214 npm91MIT
- AlicenseAqualityDmaintenanceManage posts, channels, organizations, and ideas through any MCP-compatible LLM client.227 npmMIT

chatgenius-mcpofficial
AlicenseBqualityCmaintenanceEnables MCP clients like Claude and Cursor to read and act on Instagram, Facebook, WhatsApp and SMS inboxes, contacts, appointments, flows, comment automation, Content Studio posts, market intel and a knowledge base through the ChatGenius REST API. Exposes 105 scope-capped tools, with destructive actions marked for client approval and idempotency keys guarding every write.105305 npmMIT- AlicenseBqualityBmaintenanceEnables AI agents and clients to discover accounts and channels, read scheduling and analytics data, and manage posts, content items, and templates through 41 GraphQL-backed tools with private credential profiles and confirmation-gated mutations.4127 npmAGPL 3.0
- 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-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with Novu's notification infrastructure, supporting event triggering, subscriber management, topic operations, and notification retrieval.ISC
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.