Top MCPs by Category

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.

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.

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.

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.

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.

NCP is a unified MCP platform that consolidates 50+ tools, skills, and Photons into a single, intelligent interface. It enables code-mode execution, on-demand loading, scheduling, and semantic tool discovery, dramatically reducing token usage and latency while enabling AI assistants to work with external MCPs, skills, and Photons. This documentation covers how NCP works, the available MCPs and tools, installation and integration steps for popular clients (Claude Desktop, VS Code, and more), and practical examples that demonstrate how to find, run, and compose tools across MCPs. Whether you’re building with internal MCPs or exploring external tools, NCP provides a scalable, vendor-agnostic foundation for AI-powered automation and tool orchestration.

NCP is a unified MCP platform that consolidates 50+ tools, skills, and Photons into a single, intelligent interface. It enables code-mode execution, on-demand loading, scheduling, and semantic tool discovery, dramatically reducing token usage and latency while enabling AI assistants to work with external MCPs, skills, and Photons. This documentation covers how NCP works, the available MCPs and tools, installation and integration steps for popular clients (Claude Desktop, VS Code, and more), and practical examples that demonstrate how to find, run, and compose tools across MCPs. Whether you’re building with internal MCPs or exploring external tools, NCP provides a scalable, vendor-agnostic foundation for AI-powered automation and tool orchestration.

NCP is a unified MCP platform that consolidates 50+ tools, skills, and Photons into a single, intelligent interface. It enables code-mode execution, on-demand loading, scheduling, and semantic tool discovery, dramatically reducing token usage and latency while enabling AI assistants to work with external MCPs, skills, and Photons. This documentation covers how NCP works, the available MCPs and tools, installation and integration steps for popular clients (Claude Desktop, VS Code, and more), and practical examples that demonstrate how to find, run, and compose tools across MCPs. Whether you’re building with internal MCPs or exploring external tools, NCP provides a scalable, vendor-agnostic foundation for AI-powered automation and tool orchestration.

NCP is a unified MCP platform that consolidates 50+ tools, skills, and Photons into a single, intelligent interface. It enables code-mode execution, on-demand loading, scheduling, and semantic tool discovery, dramatically reducing token usage and latency while enabling AI assistants to work with external MCPs, skills, and Photons. This documentation covers how NCP works, the available MCPs and tools, installation and integration steps for popular clients (Claude Desktop, VS Code, and more), and practical examples that demonstrate how to find, run, and compose tools across MCPs. Whether you’re building with internal MCPs or exploring external tools, NCP provides a scalable, vendor-agnostic foundation for AI-powered automation and tool orchestration.

NCP is a unified MCP platform that consolidates 50+ tools, skills, and Photons into a single, intelligent interface. It enables code-mode execution, on-demand loading, scheduling, and semantic tool discovery, dramatically reducing token usage and latency while enabling AI assistants to work with external MCPs, skills, and Photons. This documentation covers how NCP works, the available MCPs and tools, installation and integration steps for popular clients (Claude Desktop, VS Code, and more), and practical examples that demonstrate how to find, run, and compose tools across MCPs. Whether you’re building with internal MCPs or exploring external tools, NCP provides a scalable, vendor-agnostic foundation for AI-powered automation and tool orchestration.

NCP is a unified MCP platform that consolidates 50+ tools, skills, and Photons into a single, intelligent interface. It enables code-mode execution, on-demand loading, scheduling, and semantic tool discovery, dramatically reducing token usage and latency while enabling AI assistants to work with external MCPs, skills, and Photons. This documentation covers how NCP works, the available MCPs and tools, installation and integration steps for popular clients (Claude Desktop, VS Code, and more), and practical examples that demonstrate how to find, run, and compose tools across MCPs. Whether you’re building with internal MCPs or exploring external tools, NCP provides a scalable, vendor-agnostic foundation for AI-powered automation and tool orchestration.

NCP is a unified MCP platform that consolidates 50+ tools, skills, and Photons into a single, intelligent interface. It enables code-mode execution, on-demand loading, scheduling, and semantic tool discovery, dramatically reducing token usage and latency while enabling AI assistants to work with external MCPs, skills, and Photons. This documentation covers how NCP works, the available MCPs and tools, installation and integration steps for popular clients (Claude Desktop, VS Code, and more), and practical examples that demonstrate how to find, run, and compose tools across MCPs. Whether you’re building with internal MCPs or exploring external tools, NCP provides a scalable, vendor-agnostic foundation for AI-powered automation and tool orchestration.

MindsDB ships with a built-in MCP (Model Context Protocol) server that enables MCP applications to connect, unify and respond to questions over large-scale federated data. It spans databases, data warehouses, and SaaS applications, allowing you to query across diverse sources in a unified manner. The MCP server is integrated into MindsDB's architecture with the Connect-Unify-Respond philosophy, and you can learn more about MCP at docs.mindsdb.com/mcp/overview. You can install MindsDB Server via Docker Desktop or Docker, and the MCP server is part of the standard MindsDB deployment.

MindsDB ships with a built-in MCP (Model Context Protocol) server that enables MCP applications to connect, unify and respond to questions over large-scale federated data. It spans databases, data warehouses, and SaaS applications, allowing you to query across diverse sources in a unified manner. The MCP server is integrated into MindsDB's architecture with the Connect-Unify-Respond philosophy, and you can learn more about MCP at docs.mindsdb.com/mcp/overview. You can install MindsDB Server via Docker Desktop or Docker, and the MCP server is part of the standard MindsDB deployment.

MindsDB ships with a built-in MCP (Model Context Protocol) server that enables MCP applications to connect, unify and respond to questions over large-scale federated data. It spans databases, data warehouses, and SaaS applications, allowing you to query across diverse sources in a unified manner. The MCP server is integrated into MindsDB's architecture with the Connect-Unify-Respond philosophy, and you can learn more about MCP at docs.mindsdb.com/mcp/overview. You can install MindsDB Server via Docker Desktop or Docker, and the MCP server is part of the standard MindsDB deployment.

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.

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.

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.

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.

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.