@mhdd_24/ai-gateway-mcp
Related Servers
Alternatives to @mhdd_24/ai-gateway-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables querying and managing AI logs through tools like listing logs, retrieving jobs, and performing AI-powered chat queries. Also provides access to gateway security reports and guardrail testing.-
- AlicenseBqualityFmaintenanceEnables AI assistants to manage GoClaw AI gateway infrastructure through a comprehensive suite of 66 tools for managing agents, sessions, and configurations. It provides real-time gateway context and guided workflows with enterprise-grade security features like audit logging and secret scrubbing.6612MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Azure AI Foundry services through a unified interface for model exploration and deployment, knowledge indexing and search, AI evaluation, and fine-tuning operations. Supports both GitHub token-based model testing and full Azure deployment workflows.3MIT

Bifrost MCP Gatewayofficial
AlicenseNot gradedqualityBmaintenanceOpen-source MCP and LLM gateway that aggregates MCP tools behind a unified endpoint with governance, observability, and explicit execution controls.9,277Apache 2.0- AlicenseNot gradedqualityAmaintenanceUnified AI gateway that aggregates MCP tools from multiple servers and routes LLM requests with provider combos and fallback, all managed through a web UI.1MIT

urai-routerofficial
AlicenseNot gradedqualityCmaintenanceEnables MCP clients to chat through multiple LLM API keys with automatic rotation and failover, discover free and available models, inspect key health and routing, refresh catalogues, ensure a local proxy, and generate OpenCode/Kiro/skill configuration.MIT
TDQS
Scored across 4 tools
The four tools are mostly distinct: status reports health/configuration, list enumerates entities, inspect drills into one artifact, and compare contrasts two items. There is mild potential overlap between status and inspect, but descriptions are clear enough for an agent to select the intended operation.
All tool names follow the same aigw_<verb> pattern using simple, consistent verbs. This creates a predictable convention across the entire tool set.
Four tools is a reasonable, focused count for a read-only gateway observability utility. It sits slightly low for a server claiming to 'manage' providers, but the count itself is not excessive or trivial.
The tool surface only supports reading and comparing gateway entities; there are no create, update, delete, or configuration-change operations. Given the 'manage' framing, this is a significant functional gap that would prevent agents from actually managing providers.