MCP Hub & Observability Gateway avatar

MCP Hub & Observability Gateway

Pricing

from $5.00 / 1,000 tool routing & telemetries

Go to Apify Store
MCP Hub & Observability Gateway

MCP Hub & Observability Gateway

Enterprise API Gateway for the Model Context Protocol. Route, authenticate, and log AI tool executions across multiple downstream MCP servers.

Pricing

from $5.00 / 1,000 tool routing & telemetries

Rating

0.0

(0)

Developer

Neon Innovation Lab

Neon Innovation Lab

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

2 days ago

Last modified

Categories

Share

🌐 MCP Hub & Observability Gateway

An Enterprise API Gateway for the Model Context Protocol (MCP). This Actor acts as a centralized routing and observability layer for your AI agent swarms. Instead of connecting Claude or your AI clients directly to dozens of scattered backend MCP servers, you connect them to this single Hub. The Hub transparently aggregates all tools, routes execution requests to the correct downstream servers, and logs every single interaction to a PostgreSQL database for full auditability.

✨ Core Features

  • Single Unified Endpoint: Expose a single Apify Standby URL to your AI clients while routing traffic to multiple backend servers simultaneously.
  • Complete Observability: Every call_tool execution is intercepted and logged directly to your Supabase PostgreSQL database.
  • Latency Tracking: Automatically measures downstream server execution times (latency_ms) to detect bottlenecks.
  • Zero-Config SSL: Native Apify Standby integration provides secure https:// and sse:// connections instantly—no domains or Nginx proxies required.

🚀 How to Connect (For AI Clients)

To connect Claude Desktop (or any other MCP-compatible client) to the Gateway, add the following to your claude_desktop_config.json:

{
"mcpServers": {
"mcp-hub-gateway": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/inspector",
"https://YOUR_ACTOR_NAME.apify.actor/sse?token=YOUR_API_TOKEN"
]
}
}
}
🛠 Operator Configuration
When running this Actor, the Operator must provide the following inputs:
DOWNSTREAM_URLS: A comma-separated list of the backend MCP Standby URLs you want to aggregate (e.g., https://backend1.apify.actor/sse, https://backend2.apify.actor/sse).
SUPABASE_URL: Your Supabase project URL (http://...:54321).
SUPABASE_SERVICE_ROLE_KEY: Your Supabase JWT Service Key.
📊 Telemetry Data Logged
The Hub automatically writes the following telemetry data to your hub_logs table for every tool execution:
agent_id: The identifier of the calling AI client.
tool_name: The exact tool that was executed.
request_payload: The JSON arguments sent to the tool.
response_payload: The JSON result returned by the downstream server.
latency_ms: Execution time in milliseconds.
status: success or error.
error_message: Full stack trace if the downstream server fails.