33GOD Pipeline MCP Hub
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@33GOD Pipeline MCP Hublist available domains"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
33GOD Pipeline MCP Hub
A multi-domain MCP server that fronts many tool domains (Plane, BloodBank, ticket-lifecycle, …) behind one small, stable surface — so an agent isn't flooded with hundreds of tool schemas / millions of tokens.
Served at https://mcp.delo.sh/mcp (header-PAT auth).
How it works — discovery + dispatcher gating
The hub exposes only three tools to clients:
Tool | Purpose |
| List available domains (name, description, tool_count). Start here. |
| Load + list one domain's tools, each with its |
| Invoke a specific domain tool; |
Underlying domain tools are held in an internal registry and are never advertised
directly, so the per-request tool-schema cost stays tiny and constant. This works on
any MCP client regardless of notifications/tools/list_changed support.
Trade-off: domain tools are invoked through
call_domain_tool(...)rather than as native function calls. The hub validates arguments against the real tool schema and returns clear errors. (A future "native passthrough" mode could expose real prefixed tools for clients that already defer schemas, like Claude Code.)
Related MCP server: fastmcp-gateway
Domains
plane — reuses
plane-mcp-server's tools in-process (work items, projects, cycles, epics, etc.). Auth + Plane API calls use the caller's PAT from the request context.bloodbank (Phase 1) — publish/trace events on the BloodBank NATS bus.
lifecycle (Phase 2) — opinionated ticket state machine (pull → triage → … → done).
Auth
HTTP mode uses the same header scheme as plane-mcp-server:
Authorization: Bearer <PLANE_PAT>x-workspace-slug: <workspace-slug>
Run locally
# Install the hub + the plane domain dependency (from the local checkout)
uv pip install -e .
uv pip install -e ../../plane-mcp-server
# stdio (no auth; Plane tools use env fallback)
PLANE_API_KEY=... PLANE_WORKSPACE_SLUG=... python -m mcp_hub stdio
# http (header-PAT auth) on :8998 at /mcp
PLANE_INTERNAL_BASE_URL=http://localhost:8000 python -m mcp_hub httpDeploy (DeLoNET)
Docker stack at ~/docker/stacks/ai/pipeline-mcp-hub/. It builds this repo and pulls the
plane-mcp-server source via a named build context, joins the proxy network, and is
routed by Traefik at Host(mcp.delo.sh). *.delo.sh already wildcards through the
Cloudflare tunnel → Traefik.
cd ~/docker/stacks/ai/pipeline-mcp-hub
docker compose up -d --buildRequires Docker Compose ≥ v2.17 (for build.additional_contexts).
Key env
Var | Default | Purpose |
|
| Listen port inside the container |
| — | Server-to-server Plane API base; set to |
|
| Fallback Plane API base |
Phase 0 needs no secrets — the Plane PAT arrives per-request in the client's headers.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Tools
Related MCP Servers
- Alicense-qualityAmaintenanceA progressive-disclosure gateway for MCP servers that keeps tool lists small by exposing one top-level tool per server, allowing agents to search, list, inspect, and call underlying tools within a selected domain.14MIT
- Alicense-qualityAmaintenanceAggregates tools from multiple upstream MCP servers and exposes them through 4 meta-tools, enabling LLMs to discover and use hundreds of tools without loading all schemas upfront.2Apache 2.0
- Alicense-qualityDmaintenanceAggregates tools from multiple MCP servers, acting as a proxy to provide unified access to various AI agents and tools.143MIT
- Alicense-qualityCmaintenanceAn MCP server that exposes a suite of developer tools and apps via a shared tool registry, enabling agents to list and call tools through the MCP protocol.MIT
Related MCP Connectors
MCP server exposing the Backtest360 engine API as tools for AI agents.
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
Hosted MCP with 91 agent tools: X, domains, SEO, Maps, Trends, Search, YouTube, TikTok, and more.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/delorenj/33god-mcp-hub'
If you have feedback or need assistance with the MCP directory API, please join our Discord server