mcp-all-in-one
Related Servers
Alternatives to mcp-all-in-one
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA modular MCP server exposing tools for integrating with services like GitHub, Redash, Jenkins, Figma, Jira, Confluence, Teams, Datadog, PagerDuty, Slack, and Presto, enabling users to manage these platforms through natural language via an MCP client.-
- AlicenseBqualityBmaintenanceA universal MCP server enabling AI assistants to query and manage six database engines (Postgres, Redis, Elasticsearch, MySQL, MongoDB, LDAP) through 113+ tools with read-only safety and fault tolerance.10016 npm82MIT
- AlicenseNot gradedqualityDmaintenanceA production-grade MCP server designed for multi-tenant, authenticated, and observable AI agent systems, enabling secure tool execution across heterogeneous data sources.64MIT
- FlicenseBqualityBmaintenanceUnified MCP server exposing 12 DevOps tools across GitHub, PostgreSQL, Slack, and Google Calendar for AI agents, with rate limiting, input validation, and per-service scoped tokens.30-
- AlicenseAqualityBmaintenanceUnified MCP server for querying CSV, Postgres, and REST API data sources via embedded DuckDB, enabling cross-source SQL joins with no external query service.721 npmMIT
- FlicenseNot gradedqualityCmaintenanceA governed MCP server exposing Databricks operations as tools for jobs orchestration, SQL execution, notebook creation, Unity Catalog governance, lineage, clusters, and DLT pipelines, with safety features like dry-run and audit logging.-
TDQS
Scored across 4 tools
Each tool targets a distinct function: listing connections, retrieving query metadata, fetching cached results, and executing queries. Descriptions clearly differentiate them, especially the cached vs. fetch variants.
All tools follow a 'redash.<verb>_<noun>' pattern with consistent use of underscore. Minor inconsistency between 'get' and 'fetch' for result retrieval, but overall predictable.
4 tools is a small set for a Redash integration, barely covering basic operations. While not extreme, it feels slightly underpowered for typical usage.
Missing essential tools like listing queries or managing connections. Only allows reading allowlisted queries by known ID, leaving significant gaps for agent workflows.