oauth

MCP Bundles Hub MCP Server provides direct, unified access to tools from all your enabled MCP bundles through a single authenticated endpoint. It enables executing tools, discovering what tools are available across bundles, searching by name, provider, or capability, and checking readiness and details for each tool. This hub server consolidates bundle tools into one MCP interface, streamlining AI-assisted workflows by securely managing credentials and ensuring bundle-aware execution. Built with OAuth and API key authentication, it supports tool discovery, readiness checks, and detailed tool information, making it easier to scale tool access across multiple providers and bundles.

Pipedream MCP Server is a reference implementation for self-hosting a Model Context Protocol (MCP) server. It showcases how to manage and serve MCP-based apps and tools in your own environment, providing you with a way to run MCP servers locally or within your organization. Note that this MCP server is a reference implementation and is no longer actively maintained; for production workloads, Pipedream recommends using the remote MCP server, which offers hosted reliability and scaling. The server supports two primary modes and integrates with Pipedream Connect for authentication and API management, enabling automatic app discovery and credential storage with enterprise-grade security.

MetaMCP is a MCP proxy that lets you dynamically aggregate MCP servers into a unified MCP server, and apply middlewares. MetaMCP itself is a MCP server so it can be easily plugged into ANY MCP clients. It functions as an MCP Aggregator, Orchestrator, Middleware, and Gateway all in one docker image, enabling scalable, configurable hosting of multiple MCP servers behind a single endpoint with flexible authentication, tooling, and annotations. This README introduces core concepts such as MCP Server configurations, Namespaces, Endpoints, Middleware, Inspector, and Tool Overrides & Annotations, and provides quick-start guidance for running MetaMCP with Docker, building a development environment, and integrating with clients like Claude Desktop via proxies. It also covers MCP protocol compatibility, authentication options (including API keys, OAuth, and OIDC), and integration guidance for developers looking to remix MCP tool flows and middleware pipelines.