ateam-mcp
Related Servers
Alternatives to ateam-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityBmaintenanceConnects AI assistants to the Opsenes platform, exposing its capabilities as MCP tools, resources, and prompts for safe platform operations.MIT
PaidSync MCP Serverofficial
AlicenseNot gradedqualityFmaintenanceConnects Google Ads, Meta Ads, and LinkedIn Ads to AI assistants, enabling natural language ad campaign management, reporting, and optimization across platforms.MIT
HiveFlow MCP Serverofficial
AlicenseBqualityCmaintenanceConnects AI assistants (Claude, Cursor, etc.) directly to the HiveFlow automation platform, allowing them to create, manage, and execute automation flows through natural language commands.910 npm4MIT- AlicenseNot gradedqualityCmaintenanceConnects AI assistants such as Cursor, ChatGPT, and Claude to Yatishara Studio, enabling secure access and interaction with the studio's capabilities through natural language.MIT

MCPaeroeduofficial
AlicenseAqualityCmaintenanceEnables AI assistants to interact with the AeroEduVision platform, allowing exam generation, course management, knowledge graph queries, and student progress tracking through natural language commands.24MIT- AlicenseNot gradedqualityDmaintenanceConnects AI assistants to Supabase projects, enabling them to manage tables, query data, deploy Edge Functions, handle migrations, and access project resources through natural language commands.Apache 2.0
TDQS
Scored across 41 tools
Each tool targets a distinct purpose. Authentication, onboarding, CRUD for connectors/skills/solutions, various GitHub operations (patch, promote, push, pull, rollback), and multiple testing modes (skill, connector, notification, voice, pipeline) are all clearly separated. No two tools perform the same function, and descriptions are detailed enough to differentiate similar operations like ateam_build_and_run vs ateam_redeploy.
All tools share the ateam_ prefix and most follow a verb_noun pattern (e.g., ateam_create_connector, ateam_test_skill). However, a few tools use noun-only names (ateam_conversation, ateam_get_examples) or compound verbs (ateam_build_and_run), breaking the pattern slightly. Overall, the naming is largely consistent and predictable.
With 41 tools, the server exceeds the typical range of 3-15 tools for a well-scoped server. However, the domain is broad, covering authentication, CRUD, GitHub integration, testing, and admin operations, which justifies many tools. Some consolidation might be possible, but the count is borderline heavy.
The tool surface covers the full lifecycle of solution development: onboarding, authentication, creating/deleting/reading components, comprehensive GitHub operations (diff, log, patch, promote, push, pull, rollback, status), multiple testing modalities (skill, connector, notification, voice, pipeline, abort, status), and admin tools (sync_all, status_all). No obvious gaps are evident.