awesome -enterprise

Awesome MCP Enterprise is a curated directory of enterprise-grade MCP (Model Context Protocol) tools, servers, and services. It aggregates private registries, gateways, build tools, security controls, and deployment options to help organizations discover, compare, and integrate MCP solutions. Use this MCP directory as a reference to identify suitable servers and tooling for authentication, governance, tool discovery, and scalable MCP networks. The entries span gateways, registries, and enterprise-ready hosting options, making it easier to map MCP capabilities to your architecture and compliance requirements.

To leverage the content, browse the sections to find MCP servers or gateways that fit your use case, evaluate their features (auth, observability, RBAC, rate limiting, and tooling support), and then follow the installation or integration instructions provided by the individual projects. You can augment your stack by selecting a combination of private registries, gateways, and deployment patterns (containerized, cloud-hosted, or self-hosted) to build a robust MCP ecosystem for your organization.

Prerequisites:

• Git installed on your machine
• Access to a runtime suitable for your chosen MCP server (Node.js for Node-based servers, Python for uv/uvx-based deployments, etc.)
• Basic familiarity with your org's security and authentication requirements

Install steps:

1. Clone this MCP directory or repository that hosts the enterprise MCP listings: git clone https://github.com/your-org/bh-rat-awesome-mcp-enterprise.git cd bh-rat-awesome-mcp-enterprise

2. If this MCP server is Node.js based (as indicated by the mcp_config), ensure Node.js is installed. Then install dependencies if a package.json exists: npm install

3. Configure environment variables as needed. Create a .env file or export variables in your shell, for example: export MCP_DIR=/path/to/mcp/dir export MCP_AUTH_TOKEN=your-token

4. Run the MCP server using the recommended command (aligned with the mcp_config): node server.js

5. Verify the server is running (e.g., check http://localhost:3000 or the configured port) and consult the specific tooling documentation for any additional setup steps required by the enterprise entries.

Notes and tips:

• This directory is primarily a curated reference. Individual MCP servers will have their own installation and security considerations (RBAC, audit logging, rate limiting, etc.).
• Pay attention to your organization’s data governance and compliance needs when selecting gateways or registries (e.g., data residency, access controls, and logging).
• If you integrate multiple MCP servers, ensure consistent authentication and tool governance across the stack to avoid policy conflicts.
• Some entries may require enterprise subscriptions or private access; consult the vendor documentation for access levels and licensing details.